Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99c43fbc048bc413f615fb58ac6d27ead9fe37a41f3292f597228c6d4784e0fa

Tx prefix hash: dadc73ac1a7360b8783dbbdc2dc2086e352756a9912cc8415a032644b083d9c6
Tx public key: fb08cc2f1897dd034748d49f643d81af4dea5a62f6a5a0975333fd16455c70e0
Timestamp: 1733038335 Timestamp [UCT]: 2024-12-01 07:32:15 Age [y:d:h:m:s]: 00:198:19:07:02
Block: 1165560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141797 RingCT/type: yes/0
Extra: 01fb08cc2f1897dd034748d49f643d81af4dea5a62f6a5a0975333fd16455c70e0021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c0b3b43131e0e1c05f06f321825eecf009ebef3d216635e9ffa55ad731a8cec 0.600000000000 1651235 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": 1165570, "vin": [ { "gen": { "height": 1165560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c0b3b43131e0e1c05f06f321825eecf009ebef3d216635e9ffa55ad731a8cec" } } ], "extra": [ 1, 251, 8, 204, 47, 24, 151, 221, 3, 71, 72, 212, 159, 100, 61, 129, 175, 77, 234, 90, 98, 246, 165, 160, 151, 83, 51, 253, 22, 69, 92, 112, 224, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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