Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 6d815d9991ccb9aefb1ad4cf3d8b950e44dfbcf4f267fcdeb7352757e805d5aa

Tx prefix hash: c72eeda097b2622dcb9c374acc4e68ad6ce1c061363cde50824197ba83b5b24e
Tx public key: 273b447fc672e783d7a7871bff653123c8769db24366024ea200a45a814e7b71
Timestamp: 1705823610 Timestamp [UCT]: 2024-01-21 07:53:30 Age [y:d:h:m:s]: 01:087:19:43:40
Block: 939988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323882 RingCT/type: yes/0
Extra: 01273b447fc672e783d7a7871bff653123c8769db24366024ea200a45a814e7b7102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 083ba1c9b7be251c42e4f751ddcaa78b20221fdc28b63b70bbe57d97ddfab6c9 0.600000000000 1398122 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 939998, "vin": [ { "gen": { "height": 939988 } } ], "vout": [ { "amount": 600000000, "target": { "key": "083ba1c9b7be251c42e4f751ddcaa78b20221fdc28b63b70bbe57d97ddfab6c9" } } ], "extra": [ 1, 39, 59, 68, 127, 198, 114, 231, 131, 215, 167, 135, 27, 255, 101, 49, 35, 200, 118, 157, 178, 67, 102, 2, 78, 162, 0, 164, 90, 129, 78, 123, 113, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8