Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcefeed43c3865be59b2e4a516e8af15486a5b3e944642901ffc610d6c9e069d

Tx prefix hash: de16616c69c188662f44a1c30eb2359b7224bccdbdd1c8a482035a3e1b350de6
Tx public key: d488d15c03f908a6c5d3f5666a53609ce80e1949e02d8c5e7a33170241f285ed
Timestamp: 1722860877 Timestamp [UCT]: 2024-08-05 12:27:57 Age [y:d:h:m:s]: 00:223:14:31:04
Block: 1081268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159707 RingCT/type: yes/0
Extra: 01d488d15c03f908a6c5d3f5666a53609ce80e1949e02d8c5e7a33170241f285ed021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f1e63124fb0a9878156ba80820bde3f9b7e2b88fad5aaa2fda2d244e91a90ee 0.600000000000 1554951 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": 1081278, "vin": [ { "gen": { "height": 1081268 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f1e63124fb0a9878156ba80820bde3f9b7e2b88fad5aaa2fda2d244e91a90ee" } } ], "extra": [ 1, 212, 136, 209, 92, 3, 249, 8, 166, 197, 211, 245, 102, 106, 83, 96, 156, 232, 14, 25, 73, 224, 45, 140, 94, 122, 51, 23, 2, 65, 242, 133, 237, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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