Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e5136c437d9c73ceb940fd7f864efa45b0da96a3031d0bb31b84dedb560dd41

Tx prefix hash: fbcbce2a52b57f76c058eb8e18dfd4dc74e53650d6205a60843837023893e5e6
Tx public key: dcd5f2c3807472d8bb6b9b46afc8f0bf41fab9e407708c67795c4a40154696c9
Timestamp: 1717602680 Timestamp [UCT]: 2024-06-05 15:51:20 Age [y:d:h:m:s]: 01:154:10:01:14
Block: 1037684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368922 RingCT/type: yes/0
Extra: 01dcd5f2c3807472d8bb6b9b46afc8f0bf41fab9e407708c67795c4a40154696c902110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4f6891baca43961911d92c17d3fcbd8ce183b1ec38d816863f7ee543bd45d02 0.600000000000 1506237 of 15

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": 1037694, "vin": [ { "gen": { "height": 1037684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4f6891baca43961911d92c17d3fcbd8ce183b1ec38d816863f7ee543bd45d02" } } ], "extra": [ 1, 220, 213, 242, 195, 128, 116, 114, 216, 187, 107, 155, 70, 175, 200, 240, 191, 65, 250, 185, 228, 7, 112, 140, 103, 121, 92, 74, 64, 21, 70, 150, 201, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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