Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1184914c3cecacd9addde5fe50f72d9d90c5898a7457ab2c06e1c864a5948aa0

Tx prefix hash: b98a9b033697802443eafd3f57fd66051217a427821a0a2525bf6d1faa841c8a
Tx public key: 1771a35c5453a08b162ec3e1897f0a7099f8bfc42413edce66b7f6d77eafaeae
Timestamp: 1746583554 Timestamp [UCT]: 2025-05-07 02:05:54 Age [y:d:h:m:s]: 00:004:12:21:49
Block: 1277420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3231 RingCT/type: yes/0
Extra: 011771a35c5453a08b162ec3e1897f0a7099f8bfc42413edce66b7f6d77eafaeae0211000000041f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2e14f60abf25867b2209f46a492287bbca0afbf8ec98f13723811989f12e910 0.600000000000 1764775 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": 1277430, "vin": [ { "gen": { "height": 1277420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2e14f60abf25867b2209f46a492287bbca0afbf8ec98f13723811989f12e910" } } ], "extra": [ 1, 23, 113, 163, 92, 84, 83, 160, 139, 22, 46, 195, 225, 137, 127, 10, 112, 153, 248, 191, 196, 36, 19, 237, 206, 102, 183, 246, 215, 126, 175, 174, 174, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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