Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc6c8a40bc04f804db199396f6d5263a8efdc08834de480bca77fe1cdcae972d

Tx prefix hash: c0a998920b727c12e885023883caf5bccf727631059416950b654334c6fb7cd3
Tx public key: 7db96407d8e88f05797a070c9a9ce895d037477d27c1dcc1f6d55e057e23f578
Timestamp: 1675431319 Timestamp [UCT]: 2023-02-03 13:35:19 Age [y:d:h:m:s]: 02:098:22:25:40
Block: 688939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 592353 RingCT/type: yes/0
Extra: 017db96407d8e88f05797a070c9a9ce895d037477d27c1dcc1f6d55e057e23f5780211000000015029cbac000000000000000000

1 output(s) for total of 3.200803626000 dcy

stealth address amount amount idx
00: d6d69327b22830af2bdc85ee5c469bb0e6832e72ff31191b715470df860eae19 3.200803626000 1131595 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": 688949, "vin": [ { "gen": { "height": 688939 } } ], "vout": [ { "amount": 3200803626, "target": { "key": "d6d69327b22830af2bdc85ee5c469bb0e6832e72ff31191b715470df860eae19" } } ], "extra": [ 1, 125, 185, 100, 7, 216, 232, 143, 5, 121, 122, 7, 12, 154, 156, 232, 149, 208, 55, 71, 125, 39, 193, 220, 193, 246, 213, 94, 5, 126, 35, 245, 120, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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