Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0eb2f16a644649ae5fa977c11b56bfe5c0f8e6473db8f19988b665f59a0846e5

Tx prefix hash: cf047ca3d68202cfbeb1b11a30909a7bfb0e9fb9845462d8763281d37c76423d
Tx public key: fdf3c527ce0d1e8008955d86af142f0b3a9a7bd4094a91dc64bd34c4d061b50c
Timestamp: 1694264683 Timestamp [UCT]: 2023-09-09 13:04:43 Age [y:d:h:m:s]: 01:168:04:06:09
Block: 844377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381259 RingCT/type: yes/0
Extra: 01fdf3c527ce0d1e8008955d86af142f0b3a9a7bd4094a91dc64bd34c4d061b50c0211000000074b8f5122000000000000000000

1 output(s) for total of 0.977751625000 dcy

stealth address amount amount idx
00: ba6ca226ad752e0575c975676a393ba03f281650a0a7697afa2e3a524ccc0f16 0.977751625000 1297681 of 0

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": 844387, "vin": [ { "gen": { "height": 844377 } } ], "vout": [ { "amount": 977751625, "target": { "key": "ba6ca226ad752e0575c975676a393ba03f281650a0a7697afa2e3a524ccc0f16" } } ], "extra": [ 1, 253, 243, 197, 39, 206, 13, 30, 128, 8, 149, 93, 134, 175, 20, 47, 11, 58, 154, 123, 212, 9, 74, 145, 220, 100, 189, 52, 196, 208, 97, 181, 12, 2, 17, 0, 0, 0, 7, 75, 143, 81, 34, 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