Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07ad390b54f3cd9a342553f56345d97179e0717b4809b36a0964133f76a672cd

Tx prefix hash: 1d444ade38067ccd5e305a34c99a39abb03c7fcec2a54e0ba829d7f6f7b223ba
Tx public key: eb873f461b3c4de535d772340d945029d27e3b8b522ca81e22e4f11b6c5b346c
Timestamp: 1705798512 Timestamp [UCT]: 2024-01-21 00:55:12 Age [y:d:h:m:s]: 01:079:10:55:48
Block: 939779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317909 RingCT/type: yes/0
Extra: 01eb873f461b3c4de535d772340d945029d27e3b8b522ca81e22e4f11b6c5b346c0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3d32e6c3d7bb38d5a2c0f163fc78772578e0379b94848a59cfacafa2ec06e92 0.600000000000 1397911 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": 939789, "vin": [ { "gen": { "height": 939779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3d32e6c3d7bb38d5a2c0f163fc78772578e0379b94848a59cfacafa2ec06e92" } } ], "extra": [ 1, 235, 135, 63, 70, 27, 60, 77, 229, 53, 215, 114, 52, 13, 148, 80, 41, 210, 126, 59, 139, 82, 44, 168, 30, 34, 228, 241, 27, 108, 91, 52, 108, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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