Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2007e3e867b6cf5f4c87b556f72a6666941d8e7e30711f8a9a0f2b142c68ef7

Tx prefix hash: fef9189a3156792d9b7973d20b7ed31b972f58990eebe6729ce34ec34b9dd987
Tx public key: dd4d4383ae7155b9007bde1e63fbf849221d2f2616ce5cf7404352f538d59d58
Timestamp: 1710351935 Timestamp [UCT]: 2024-03-13 17:45:35 Age [y:d:h:m:s]: 00:242:12:40:12
Block: 977585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173617 RingCT/type: yes/0
Extra: 01dd4d4383ae7155b9007bde1e63fbf849221d2f2616ce5cf7404352f538d59d580211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d6b477b5e5f33047f48ababac1a4ad4b35ac0ecc3493ea1c458817eaadecb2a 0.600000000000 1437588 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": 977595, "vin": [ { "gen": { "height": 977585 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d6b477b5e5f33047f48ababac1a4ad4b35ac0ecc3493ea1c458817eaadecb2a" } } ], "extra": [ 1, 221, 77, 67, 131, 174, 113, 85, 185, 0, 123, 222, 30, 99, 251, 248, 73, 34, 29, 47, 38, 22, 206, 92, 247, 64, 67, 82, 245, 56, 213, 157, 88, 2, 17, 0, 0, 0, 7, 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