Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c5fd5d26a2a41cfdc7031179460d7a975cb1f7e96a3bcce2938ea51ba349ebd

Tx prefix hash: ffa6b7b4f9b066d0d3739821815819fe45ad923e32098c2bc34af2555d3b28c6
Tx public key: 0d327f0a91d3a5e70c1feacab55f8474c60a3a1cf133aa8d5b93ce58bf9ed6a9
Timestamp: 1682309450 Timestamp [UCT]: 2023-04-24 04:10:50 Age [y:d:h:m:s]: 01:360:00:54:33
Block: 745332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518587 RingCT/type: yes/0
Extra: 010d327f0a91d3a5e70c1feacab55f8474c60a3a1cf133aa8d5b93ce58bf9ed6a9021100000003e7ace25d000000000000000000

1 output(s) for total of 2.081641282000 dcy

stealth address amount amount idx
00: b8e2b7b88e4fa4308153644ee364abf350e22240d5b3024a4301351d3d2032dc 2.081641282000 1192773 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": 745342, "vin": [ { "gen": { "height": 745332 } } ], "vout": [ { "amount": 2081641282, "target": { "key": "b8e2b7b88e4fa4308153644ee364abf350e22240d5b3024a4301351d3d2032dc" } } ], "extra": [ 1, 13, 50, 127, 10, 145, 211, 165, 231, 12, 31, 234, 202, 181, 95, 132, 116, 198, 10, 58, 28, 241, 51, 170, 141, 91, 147, 206, 88, 191, 158, 214, 169, 2, 17, 0, 0, 0, 3, 231, 172, 226, 93, 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