Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc9a705dcb2ea7e107edc5c9a30004484a0a3ee5410030fdead4ead8493c429e

Tx prefix hash: f3325b20ae0d4a5e2e7072fbd1b2caf79f38891c6ac2869793f06f2a7c7459d7
Tx public key: 3419fc913372edbf16f6bdad08396fb03a537a39dd064352dd399a867ac6a6e4
Timestamp: 1745494117 Timestamp [UCT]: 2025-04-24 11:28:37 Age [y:d:h:m:s]: 00:017:05:54:32
Block: 1268407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12329 RingCT/type: yes/0
Extra: 013419fc913372edbf16f6bdad08396fb03a537a39dd064352dd399a867ac6a6e4021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9fdd17c7258ac70085756181ff45e4e0bfcf9ad1b9a4e8ebf30db9292e078e0 0.600000000000 1755636 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": 1268417, "vin": [ { "gen": { "height": 1268407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9fdd17c7258ac70085756181ff45e4e0bfcf9ad1b9a4e8ebf30db9292e078e0" } } ], "extra": [ 1, 52, 25, 252, 145, 51, 114, 237, 191, 22, 246, 189, 173, 8, 57, 111, 176, 58, 83, 122, 57, 221, 6, 67, 82, 221, 57, 154, 134, 122, 198, 166, 228, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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