Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e04c52af7f00f194f8fa64e2a63aa961ae5127304934990886e91455fa204ce

Tx prefix hash: bf939991e64b918ea19cac925917832ebacaa0f30bc26cc9d260a2a696b7a3a0
Tx public key: fc911d0b158cdaf1f94a880ef5a5f07e18c0a563d8686471780a8cb40f83eb9a
Timestamp: 1762786033 Timestamp [UCT]: 2025-11-10 14:47:13 Age [y:d:h:m:s]: 00:043:09:19:16
Block: 1409150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31050 RingCT/type: yes/0
Extra: 01fc911d0b158cdaf1f94a880ef5a5f07e18c0a563d8686471780a8cb40f83eb9a02110000000401491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91f6ca059daffe78c81712b189e625b097fcd9b0798fead715a199bed30bd5e8 0.600000000000 1897583 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": 1409160, "vin": [ { "gen": { "height": 1409150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91f6ca059daffe78c81712b189e625b097fcd9b0798fead715a199bed30bd5e8" } } ], "extra": [ 1, 252, 145, 29, 11, 21, 140, 218, 241, 249, 74, 136, 14, 245, 165, 240, 126, 24, 192, 165, 99, 216, 104, 100, 113, 120, 10, 140, 180, 15, 131, 235, 154, 2, 17, 0, 0, 0, 4, 1, 73, 31, 136, 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