Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b552e643c99b0beb1db50d0f34470e1dda7c82e15649c6edaefa88c9edeb13f7

Tx prefix hash: 2745baf7be0c9c04eb04ead9ab041f5c1d24a9d26f4d176f2d6fb8746303be4f
Tx public key: 824b497bf3c3e28953d72a7e175d2370ed055d6a70a14f2e235e687c0f0a49b8
Timestamp: 1646681852 Timestamp [UCT]: 2022-03-07 19:37:32 Age [y:d:h:m:s]: 02:291:04:04:51
Block: 453471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 727617 RingCT/type: yes/0
Extra: 01824b497bf3c3e28953d72a7e175d2370ed055d6a70a14f2e235e687c0f0a49b802110000000b4da16a3a000000000000000000

1 output(s) for total of 19.295791864000 dcy

stealth address amount amount idx
00: 8926583ab6fd1a7e6049013ab954280bfdff379039aa0d0df9d4a8858562ab65 19.295791864000 868942 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": 453481, "vin": [ { "gen": { "height": 453471 } } ], "vout": [ { "amount": 19295791864, "target": { "key": "8926583ab6fd1a7e6049013ab954280bfdff379039aa0d0df9d4a8858562ab65" } } ], "extra": [ 1, 130, 75, 73, 123, 243, 195, 226, 137, 83, 215, 42, 126, 23, 93, 35, 112, 237, 5, 93, 106, 112, 161, 79, 46, 35, 94, 104, 124, 15, 10, 73, 184, 2, 17, 0, 0, 0, 11, 77, 161, 106, 58, 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