Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3e9d7c0eec5e78d50c52890ed7353b97c8db23bf525b56323c8f3d0f2a3a10e

Tx prefix hash: b1539005172a40ae063dee5b3d86846fa51d055ef72ae5f9d36d09ac59479757
Tx public key: 38d991649efdf9446fff05013c3b1c3fa0d9f676b22b16675644e0fbe8023e20
Timestamp: 1706377034 Timestamp [UCT]: 2024-01-27 17:37:14 Age [y:d:h:m:s]: 01:085:22:56:34
Block: 944589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322533 RingCT/type: yes/0
Extra: 0138d991649efdf9446fff05013c3b1c3fa0d9f676b22b16675644e0fbe8023e2002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b63ee376b46db2f800c65fa980a8052a32856e2ef2492f5515f0596deb7b904 0.600000000000 1402871 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": 944599, "vin": [ { "gen": { "height": 944589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b63ee376b46db2f800c65fa980a8052a32856e2ef2492f5515f0596deb7b904" } } ], "extra": [ 1, 56, 217, 145, 100, 158, 253, 249, 68, 111, 255, 5, 1, 60, 59, 28, 63, 160, 217, 246, 118, 178, 43, 22, 103, 86, 68, 224, 251, 232, 2, 62, 32, 2, 17, 0, 0, 0, 1, 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