Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c653305d829be2c89d52245a153b7f52ce61f17b0341ae896f564098571afb0a

Tx prefix hash: 35cb80a8ab66e6ea6d6f2deb4e06058b1b40fa0212963dc54884d52da214058a
Tx public key: 75114f11b962f6351d5fc30bbbe0872b8a13bc435d5bba3fa3b6044fe9dfce64
Timestamp: 1713282129 Timestamp [UCT]: 2024-04-16 15:42:09 Age [y:d:h:m:s]: 00:231:17:31:43
Block: 1001840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165904 RingCT/type: yes/0
Extra: 0175114f11b962f6351d5fc30bbbe0872b8a13bc435d5bba3fa3b6044fe9dfce640211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8e753337b373f04ec802bf6042114bc8922a2a0cec1658f6729c4f1e8fbf20c 0.600000000000 1462352 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": 1001850, "vin": [ { "gen": { "height": 1001840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8e753337b373f04ec802bf6042114bc8922a2a0cec1658f6729c4f1e8fbf20c" } } ], "extra": [ 1, 117, 17, 79, 17, 185, 98, 246, 53, 29, 95, 195, 11, 187, 224, 135, 43, 138, 19, 188, 67, 93, 91, 186, 63, 163, 182, 4, 79, 233, 223, 206, 100, 2, 17, 0, 0, 0, 3, 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