Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8a911c6c66510cd64c6997bd828d6de441d9a4859270da07e2b1724c1437373

Tx prefix hash: 1d162e2dbb48afff0b1ec41693a714d80d74e3ee90d073f8decceccc3b4892aa
Tx public key: 17c650a5109892ce1fe97b3bbe18d868d17452e1cd0451f1723af91aa21d4e2e
Timestamp: 1734153162 Timestamp [UCT]: 2024-12-14 05:12:42 Age [y:d:h:m:s]: 00:186:19:30:57
Block: 1174797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133211 RingCT/type: yes/0
Extra: 0117c650a5109892ce1fe97b3bbe18d868d17452e1cd0451f1723af91aa21d4e2e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f44cf154ac8319c5dd5b1ecefa38fd1eb08c5a73cdd8a7c9cc751cd5e2f19387 0.600000000000 1660994 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": 1174807, "vin": [ { "gen": { "height": 1174797 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f44cf154ac8319c5dd5b1ecefa38fd1eb08c5a73cdd8a7c9cc751cd5e2f19387" } } ], "extra": [ 1, 23, 198, 80, 165, 16, 152, 146, 206, 31, 233, 123, 59, 190, 24, 216, 104, 209, 116, 82, 225, 205, 4, 81, 241, 114, 58, 249, 26, 162, 29, 78, 46, 2, 17, 0, 0, 0, 2, 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