Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1befefcb82cc0d4f44829bc2f44f3422de769e6e9b95093973005f8c56084bb

Tx prefix hash: 867a7ed5860df780183f68a4f1e672e3ef729f849815918b2e80da11f5f4c2e6
Tx public key: 3775f6463059c5fc63b7b2d889edbaaf69a92d5484cd5446fe05fc2b0f9a1b5b
Timestamp: 1733491656 Timestamp [UCT]: 2024-12-06 13:27:36 Age [y:d:h:m:s]: 00:157:17:23:10
Block: 1169306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112543 RingCT/type: yes/0
Extra: 013775f6463059c5fc63b7b2d889edbaaf69a92d5484cd5446fe05fc2b0f9a1b5b0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 155607dfbe4acabb45739d6afb20cae5fbe585569fb3d4935dc45fa7b4b76fac 0.600000000000 1655021 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": 1169316, "vin": [ { "gen": { "height": 1169306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "155607dfbe4acabb45739d6afb20cae5fbe585569fb3d4935dc45fa7b4b76fac" } } ], "extra": [ 1, 55, 117, 246, 70, 48, 89, 197, 252, 99, 183, 178, 216, 137, 237, 186, 175, 105, 169, 45, 84, 132, 205, 84, 70, 254, 5, 252, 43, 15, 154, 27, 91, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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