Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f8bd79ffcf1f39bf6df1293123dde84c46c76f73fc4ea994c42283d6408a634

Tx prefix hash: f400a01e23f7af1a59c2b008e339316cd50ed4b777bbceada2c2c74aa378cbe7
Tx public key: 4420a1f81e3eb5e1a8139003ff90da6820c7b2331d5dc454ec245b4b545f3884
Timestamp: 1729391873 Timestamp [UCT]: 2024-10-20 02:37:53 Age [y:d:h:m:s]: 00:245:05:46:38
Block: 1135409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174922 RingCT/type: yes/0
Extra: 014420a1f81e3eb5e1a8139003ff90da6820c7b2331d5dc454ec245b4b545f38840211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2228d8341b28bebaf1ee5f6f9b65980b2ed592b6362f29722114d9e9622e355e 0.600000000000 1618746 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": 1135419, "vin": [ { "gen": { "height": 1135409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2228d8341b28bebaf1ee5f6f9b65980b2ed592b6362f29722114d9e9622e355e" } } ], "extra": [ 1, 68, 32, 161, 248, 30, 62, 181, 225, 168, 19, 144, 3, 255, 144, 218, 104, 32, 199, 178, 51, 29, 93, 196, 84, 236, 36, 91, 75, 84, 95, 56, 132, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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