Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c1f464eb963392ec62cec8ed6183c9b00a0a76ac56ea068b6eb13f36c542b2d

Tx prefix hash: ba6b5e04627789b1d32014deeced93f20c9d2b4b779389bda39266f6abf7a1c7
Tx public key: 0185a76fb6caca1733c056a8621e97cf991aa9327033c2c2d1b73166a782db25
Timestamp: 1648653161 Timestamp [UCT]: 2022-03-30 15:12:41 Age [y:d:h:m:s]: 02:271:14:01:08
Block: 469651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 713727 RingCT/type: yes/0
Extra: 010185a76fb6caca1733c056a8621e97cf991aa9327033c2c2d1b73166a782db250211000000202e6b1fd5000000000000000000

1 output(s) for total of 17.054992218000 dcy

stealth address amount amount idx
00: 24f74a9937a58eef5d07f82dbdd788e34a73e9b15f5208dedb7f2c19c2d11dc4 17.054992218000 888635 of 0

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": 469661, "vin": [ { "gen": { "height": 469651 } } ], "vout": [ { "amount": 17054992218, "target": { "key": "24f74a9937a58eef5d07f82dbdd788e34a73e9b15f5208dedb7f2c19c2d11dc4" } } ], "extra": [ 1, 1, 133, 167, 111, 182, 202, 202, 23, 51, 192, 86, 168, 98, 30, 151, 207, 153, 26, 169, 50, 112, 51, 194, 194, 209, 183, 49, 102, 167, 130, 219, 37, 2, 17, 0, 0, 0, 32, 46, 107, 31, 213, 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