Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1418f1ebee5b4946228844f1f036b41518cb71d48fcdea16fd4b3f750b84abc8

Tx prefix hash: 33d16dd2f7d259cc08e67fa80bfb43ff669f66b0c1bb4081f869b3d927908aba
Tx public key: 5fd6850a83bafc3b6ddae17bde923a9bcd5601af98e38c58e15e5fcd0d3c34ab
Timestamp: 1716750183 Timestamp [UCT]: 2024-05-26 19:03:03 Age [y:d:h:m:s]: 01:177:06:35:23
Block: 1030624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385296 RingCT/type: yes/0
Extra: 015fd6850a83bafc3b6ddae17bde923a9bcd5601af98e38c58e15e5fcd0d3c34ab02110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85b55767e0cc0e00ebbd479ef1a22ac2b0d6257aba396cc97ed9eb4573bb16dd 0.600000000000 1498881 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": 1030634, "vin": [ { "gen": { "height": 1030624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85b55767e0cc0e00ebbd479ef1a22ac2b0d6257aba396cc97ed9eb4573bb16dd" } } ], "extra": [ 1, 95, 214, 133, 10, 131, 186, 252, 59, 109, 218, 225, 123, 222, 146, 58, 155, 205, 86, 1, 175, 152, 227, 140, 88, 225, 94, 95, 205, 13, 60, 52, 171, 2, 17, 0, 0, 0, 10, 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