Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96f5de05eebe9fca25e447394933f2da76ea99c9940ca78eaa23e8bb1124aae9

Tx prefix hash: 9fd1b62dc7e4070dcd75cc99dc05261d96a40c67874411715e308bc74e151479
Tx public key: 716579ef8f04f83b7c3ed429695b854839ddc6bcb3218dc4727bc39f5f904a85
Timestamp: 1711323916 Timestamp [UCT]: 2024-03-24 23:45:16 Age [y:d:h:m:s]: 01:050:17:12:21
Block: 985649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297227 RingCT/type: yes/0
Extra: 01716579ef8f04f83b7c3ed429695b854839ddc6bcb3218dc4727bc39f5f904a850211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6002176bcdcbec60e699224f1cb927955b7561ef5fddea07d533d96dab2b8e9 0.600000000000 1445866 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": 985659, "vin": [ { "gen": { "height": 985649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6002176bcdcbec60e699224f1cb927955b7561ef5fddea07d533d96dab2b8e9" } } ], "extra": [ 1, 113, 101, 121, 239, 143, 4, 248, 59, 124, 62, 212, 41, 105, 91, 133, 72, 57, 221, 198, 188, 179, 33, 141, 196, 114, 123, 195, 159, 95, 144, 74, 133, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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