Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f0822310781f7d95765e55727a817869796a58e9781bb1df64d1dccfc2990b1

Tx prefix hash: 1c3f8d636af2c975a40e83145fd0765b2be885cd6f70783093e36fbf45830a23
Tx public key: df1af0e9702a9dd5b6e51241432a48f6f7f81ea3fccf4d5c89bbbcc8e1bc2de3
Timestamp: 1717465012 Timestamp [UCT]: 2024-06-04 01:36:52 Age [y:d:h:m:s]: 00:311:19:38:21
Block: 1036540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222861 RingCT/type: yes/0
Extra: 01df1af0e9702a9dd5b6e51241432a48f6f7f81ea3fccf4d5c89bbbcc8e1bc2de30211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59b1064f25f97b4ece0aaf841bdcbf2e4620c227cf7b18d48c81b29e4e67f972 0.600000000000 1505067 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": 1036550, "vin": [ { "gen": { "height": 1036540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59b1064f25f97b4ece0aaf841bdcbf2e4620c227cf7b18d48c81b29e4e67f972" } } ], "extra": [ 1, 223, 26, 240, 233, 112, 42, 157, 213, 182, 229, 18, 65, 67, 42, 72, 246, 247, 248, 30, 163, 252, 207, 77, 92, 137, 187, 188, 200, 225, 188, 45, 227, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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