Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28f1fc8b18d2c21eb07d4d0aba2a541a3c9bd4f266a8803f35476ae5ea59d7fe

Tx prefix hash: 2e84570cdbb389a913481d58e2efb0bf8507594907dfd64b0b7c75734f07fe97
Tx public key: f8fde3f6ec674bcfa1797e205b58f06b908d137111a91ad7a3f69cb978a1d457
Timestamp: 1583639767 Timestamp [UCT]: 2020-03-08 03:56:07 Age [y:d:h:m:s]: 04:295:03:16:11
Block: 78527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1105606 RingCT/type: yes/0
Extra: 01f8fde3f6ec674bcfa1797e205b58f06b908d137111a91ad7a3f69cb978a1d45702110000001ee89b4e54000000000000000000

1 output(s) for total of 337.138416767000 dcy

stealth address amount amount idx
00: 1e369b179912d31c915f2b719e3cd22f9318acb0db1c237a36f7267f92c77d97 337.138416767000 143989 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": 78537, "vin": [ { "gen": { "height": 78527 } } ], "vout": [ { "amount": 337138416767, "target": { "key": "1e369b179912d31c915f2b719e3cd22f9318acb0db1c237a36f7267f92c77d97" } } ], "extra": [ 1, 248, 253, 227, 246, 236, 103, 75, 207, 161, 121, 126, 32, 91, 88, 240, 107, 144, 141, 19, 113, 17, 169, 26, 215, 163, 246, 156, 185, 120, 161, 212, 87, 2, 17, 0, 0, 0, 30, 232, 155, 78, 84, 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