Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85f8277fccd27c4d4d5a4ae39b3e80ccb6f2094b23158f9b64b9655af6989086

Tx prefix hash: dffdc8ee81f3010e68fa97ec9d84a21f04a80f55ba9783d57332c01d928ce566
Tx public key: 4887e285dc5da42bc9efc22b3fa0b78f7be4c67f85d3b15997168f4d32898ece
Timestamp: 1734278444 Timestamp [UCT]: 2024-12-15 16:00:44 Age [y:d:h:m:s]: 00:119:04:53:17
Block: 1175840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84976 RingCT/type: yes/0
Extra: 014887e285dc5da42bc9efc22b3fa0b78f7be4c67f85d3b15997168f4d32898ece0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 542d5bbabd63b4af3594a198dadc8c8c3704badc3e44b02f5a4d686c9c88aade 0.600000000000 1662165 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": 1175850, "vin": [ { "gen": { "height": 1175840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "542d5bbabd63b4af3594a198dadc8c8c3704badc3e44b02f5a4d686c9c88aade" } } ], "extra": [ 1, 72, 135, 226, 133, 220, 93, 164, 43, 201, 239, 194, 43, 63, 160, 183, 143, 123, 228, 198, 127, 133, 211, 177, 89, 151, 22, 143, 77, 50, 137, 142, 206, 2, 17, 0, 0, 0, 5, 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