Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21a7402f4fdbf1caca7137cd3a5e25d483c12a60d1144ee51b3c30da9ceb120f

Tx prefix hash: 06ec502a4c57bd20532b220bfe476704aebeffc7e86ee209d558c452fcb19dad
Tx public key: 5491f87c5db7af2fb7a310206ae62242c9a1700cec1f37b729d5887308375db7
Timestamp: 1695443044 Timestamp [UCT]: 2023-09-23 04:24:04 Age [y:d:h:m:s]: 01:197:23:01:41
Block: 854161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402538 RingCT/type: yes/0
Extra: 015491f87c5db7af2fb7a310206ae62242c9a1700cec1f37b729d5887308375db702110000000475e3f0e9000000000000000000

1 output(s) for total of 0.907423617000 dcy

stealth address amount amount idx
00: 0197109893972659ea549ab937725800fc1bae58ae447b0fe87a58ae5f4f1d1d 0.907423617000 1308119 of 0

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": 854171, "vin": [ { "gen": { "height": 854161 } } ], "vout": [ { "amount": 907423617, "target": { "key": "0197109893972659ea549ab937725800fc1bae58ae447b0fe87a58ae5f4f1d1d" } } ], "extra": [ 1, 84, 145, 248, 124, 93, 183, 175, 47, 183, 163, 16, 32, 106, 230, 34, 66, 201, 161, 112, 12, 236, 31, 55, 183, 41, 213, 136, 115, 8, 55, 93, 183, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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