Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61ec82ff1b4ab5dd16c6bea16690342819598896481a52443b91fd8d4c4874ce

Tx prefix hash: ff01159656c091f42c0687a1a8fa9e5e40b0508f00fa462551e171a2af29e19f
Tx public key: 2b4aaa70dc8b0e557421cd36720f422acc1b533d79a63b0a54176836f3afb6e4
Timestamp: 1736156788 Timestamp [UCT]: 2025-01-06 09:46:28 Age [y:d:h:m:s]: 00:348:18:31:57
Block: 1191386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246818 RingCT/type: yes/0
Extra: 012b4aaa70dc8b0e557421cd36720f422acc1b533d79a63b0a54176836f3afb6e402110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ccb3113e6e06812ad0bb5ef6a1de7fae324a5dedff66cfec4d520aa9d553eda6 0.600000000000 1677915 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": 1191396, "vin": [ { "gen": { "height": 1191386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ccb3113e6e06812ad0bb5ef6a1de7fae324a5dedff66cfec4d520aa9d553eda6" } } ], "extra": [ 1, 43, 74, 170, 112, 220, 139, 14, 85, 116, 33, 205, 54, 114, 15, 66, 42, 204, 27, 83, 61, 121, 166, 59, 10, 84, 23, 104, 54, 243, 175, 182, 228, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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