Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1eeb5406cd319f226e88a824832f8ee90c38471199f14a30eb446e0011d623b

Tx prefix hash: 6f33a1af7075d37f2ae21241ca3f0f6486c0028176add953e7c5966ebf84a8ef
Tx public key: f33fb250967393f8f5b6a419cc6b1a4b5b340d62d809fb34e293c8c4a61cacdc
Timestamp: 1746023211 Timestamp [UCT]: 2025-04-30 14:26:51 Age [y:d:h:m:s]: 00:193:07:38:24
Block: 1272776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135881 RingCT/type: yes/0
Extra: 01f33fb250967393f8f5b6a419cc6b1a4b5b340d62d809fb34e293c8c4a61cacdc0211000000069f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7827152e654c95bdb0816ff79929dfd723a41f98dc9a4588e60b33c25bdb3d3d 0.600000000000 1760051 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": 1272786, "vin": [ { "gen": { "height": 1272776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7827152e654c95bdb0816ff79929dfd723a41f98dc9a4588e60b33c25bdb3d3d" } } ], "extra": [ 1, 243, 63, 178, 80, 150, 115, 147, 248, 245, 182, 164, 25, 204, 107, 26, 75, 91, 52, 13, 98, 216, 9, 251, 52, 226, 147, 200, 196, 166, 28, 172, 220, 2, 17, 0, 0, 0, 6, 159, 159, 230, 140, 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