Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0565f7c56b58eaa0b9695c39ee184e7662a05ddac52129ca6ae8e669b1a06954

Tx prefix hash: 80a74eb363c08c4e742f8bde68bed5a102773593a1aa13ca14b26ecac376f8f3
Tx public key: b2854c8ce804e1f6e155d724b9b8d93a9fc945d69f1636b9b242f42d8e99d480
Timestamp: 1705099288 Timestamp [UCT]: 2024-01-12 22:41:28 Age [y:d:h:m:s]: 01:067:06:19:45
Block: 934008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309181 RingCT/type: yes/0
Extra: 01b2854c8ce804e1f6e155d724b9b8d93a9fc945d69f1636b9b242f42d8e99d48002110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c41d5558790cd6defd7c90d2bf60d43845019e0cba1464c4112e6bea86c1985 0.600000000000 1391992 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": 934018, "vin": [ { "gen": { "height": 934008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c41d5558790cd6defd7c90d2bf60d43845019e0cba1464c4112e6bea86c1985" } } ], "extra": [ 1, 178, 133, 76, 140, 232, 4, 225, 246, 225, 85, 215, 36, 185, 184, 217, 58, 159, 201, 69, 214, 159, 22, 54, 185, 178, 66, 244, 45, 142, 153, 212, 128, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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