Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcfd297030f560b33315fdb507bf71cf8875d193a19a0a57d83c919714888d88

Tx prefix hash: 939e4e24a97424f780e9b1cef4d042eeba936216f13d3b1cfbc97d10f86fd849
Tx public key: f5c7f999665f20c8804ec692337c810bde070b5454e9dcc598f4b10bc3c4f6c1
Timestamp: 1727641675 Timestamp [UCT]: 2024-09-29 20:27:55 Age [y:d:h:m:s]: 00:104:14:10:55
Block: 1120914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74776 RingCT/type: yes/0
Extra: 01f5c7f999665f20c8804ec692337c810bde070b5454e9dcc598f4b10bc3c4f6c1021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbea0ef028e008ac4dc9a832c8fd4c4a06e2e7fde3ac94bb341c1198425329cc 0.600000000000 1602997 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": 1120924, "vin": [ { "gen": { "height": 1120914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbea0ef028e008ac4dc9a832c8fd4c4a06e2e7fde3ac94bb341c1198425329cc" } } ], "extra": [ 1, 245, 199, 249, 153, 102, 95, 32, 200, 128, 78, 198, 146, 51, 124, 129, 11, 222, 7, 11, 84, 84, 233, 220, 197, 152, 244, 177, 11, 195, 196, 246, 193, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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