Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfbf0ac496167e3fdce6f9480929394da28b0e1468b1ea12ea6f9b80704bdf6a

Tx prefix hash: 981bbc3bf7651d31560a40eefce37a8c7837cc86713e807cc468ba425d173745
Tx public key: 5ecf07cd80bcfc10e4a0d211ebfb891c3571db5d7aca9dda5a16581ad1dc674b
Timestamp: 1716591628 Timestamp [UCT]: 2024-05-24 23:00:28 Age [y:d:h:m:s]: 00:326:05:40:15
Block: 1029300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233169 RingCT/type: yes/0
Extra: 015ecf07cd80bcfc10e4a0d211ebfb891c3571db5d7aca9dda5a16581ad1dc674b02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f9c9114d9c5728a6d3d71d4ec6830135b980b0f14eb33295bdefa33875a47d9 0.600000000000 1497351 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": 1029310, "vin": [ { "gen": { "height": 1029300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f9c9114d9c5728a6d3d71d4ec6830135b980b0f14eb33295bdefa33875a47d9" } } ], "extra": [ 1, 94, 207, 7, 205, 128, 188, 252, 16, 228, 160, 210, 17, 235, 251, 137, 28, 53, 113, 219, 93, 122, 202, 157, 218, 90, 22, 88, 26, 209, 220, 103, 75, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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