Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7083f31c080eb3b10a9bc7bc841da2a0bdd427c8572da945628a697b3143e665

Tx prefix hash: ea01c14e1b617ea3b478c41b57654f090b0c5485961558e71e2664396ff1ac68
Tx public key: f24707b243f094809ca25a43aebd6c94b358389fb595400e7959f2c0cf886937
Timestamp: 1639430883 Timestamp [UCT]: 2021-12-13 21:28:03 Age [y:d:h:m:s]: 03:016:23:01:35
Block: 394877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 791076 RingCT/type: yes/0
Extra: 01f24707b243f094809ca25a43aebd6c94b358389fb595400e7959f2c0cf886937021100000005e60c8f99000000000000000000

1 output(s) for total of 30.173026091000 dcy

stealth address amount amount idx
00: a0a85cb20a9f31d75ca829cdfba5d14b378526c48732d5a3370a0164442c4728 30.173026091000 792614 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": 394887, "vin": [ { "gen": { "height": 394877 } } ], "vout": [ { "amount": 30173026091, "target": { "key": "a0a85cb20a9f31d75ca829cdfba5d14b378526c48732d5a3370a0164442c4728" } } ], "extra": [ 1, 242, 71, 7, 178, 67, 240, 148, 128, 156, 162, 90, 67, 174, 189, 108, 148, 179, 88, 56, 159, 181, 149, 64, 14, 121, 89, 242, 192, 207, 136, 105, 55, 2, 17, 0, 0, 0, 5, 230, 12, 143, 153, 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