Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39bd4cb11731a193b2d1367ea4982ee43db5fd1715cb1694858ea0cfb67ed7a0

Tx prefix hash: fa2a73b4d9ed17802d8c47876dd09f09e2e983cccbf2ef68f3aa8216c12ce24d
Tx public key: bc54e0893790c343038889ef697b214783a5deeb895c64e832d0f957b57c0fed
Timestamp: 1737177952 Timestamp [UCT]: 2025-01-18 05:25:52 Age [y:d:h:m:s]: 00:058:05:46:34
Block: 1199819 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41415 RingCT/type: yes/0
Extra: 01bc54e0893790c343038889ef697b214783a5deeb895c64e832d0f957b57c0fed0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eae17a1f5551f63f8e39a11c42773f3402a8f97a043d981871e6ea9afbd2a640 0.600000000000 1686452 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": 1199829, "vin": [ { "gen": { "height": 1199819 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eae17a1f5551f63f8e39a11c42773f3402a8f97a043d981871e6ea9afbd2a640" } } ], "extra": [ 1, 188, 84, 224, 137, 55, 144, 195, 67, 3, 136, 137, 239, 105, 123, 33, 71, 131, 165, 222, 235, 137, 92, 100, 232, 50, 208, 249, 87, 181, 124, 15, 237, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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