Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2b84fcfd00a3782a7b9be05ed75e03345ab6cebd1810ac7ece84194bab85810

Tx prefix hash: 4ca5ff4c5efefe2f2d61770a79dfae7f38b6ca30090585ebbe874f0481ce4fb8
Tx public key: 937ecef029b643a1115873618bf06ee208a034f0b82e58d85c6c0f669f3a6c7c
Timestamp: 1709887404 Timestamp [UCT]: 2024-03-08 08:43:24 Age [y:d:h:m:s]: 01:078:06:31:06
Block: 973732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316967 RingCT/type: yes/0
Extra: 01937ecef029b643a1115873618bf06ee208a034f0b82e58d85c6c0f669f3a6c7c02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf5da60a674851faa4a8486278ae8a2dcd129eae63384dcfdeecd740e2a3bda1 0.600000000000 1433671 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": 973742, "vin": [ { "gen": { "height": 973732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf5da60a674851faa4a8486278ae8a2dcd129eae63384dcfdeecd740e2a3bda1" } } ], "extra": [ 1, 147, 126, 206, 240, 41, 182, 67, 161, 17, 88, 115, 97, 139, 240, 110, 226, 8, 160, 52, 240, 184, 46, 88, 216, 92, 108, 15, 102, 159, 58, 108, 124, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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