Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b61d5ff96a021bc037c8c19e80a8f7c075cf08fd52242230460fff0742e435f2

Tx prefix hash: 91609243501b6a1289e2fbbfaeef41d39e7a89770c604124a95fc84368df992e
Tx public key: 03dec5f11d6e6c6b3f8890648dc084815b9014d47eeac6c92e389a7c68a05ebe
Timestamp: 1716936791 Timestamp [UCT]: 2024-05-28 22:53:11 Age [y:d:h:m:s]: 00:307:02:11:21
Block: 1032156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219479 RingCT/type: yes/0
Extra: 0103dec5f11d6e6c6b3f8890648dc084815b9014d47eeac6c92e389a7c68a05ebe0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49413f88b61094d9fdb01d91a2ea2bbc0acad48d6f2c38b14d05aa7033b84108 0.600000000000 1500605 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": 1032166, "vin": [ { "gen": { "height": 1032156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49413f88b61094d9fdb01d91a2ea2bbc0acad48d6f2c38b14d05aa7033b84108" } } ], "extra": [ 1, 3, 222, 197, 241, 29, 110, 108, 107, 63, 136, 144, 100, 141, 192, 132, 129, 91, 144, 20, 212, 126, 234, 198, 201, 46, 56, 154, 124, 104, 160, 94, 190, 2, 17, 0, 0, 0, 2, 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