Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f4142de4ef1452c7f93f7e9492c975ffae078b9021fd2724ee4b020e2d7e261

Tx prefix hash: 443ad37f5775f2a4a2775c33ae53da3f95834eb9e5780526b67266d6eb770df8
Tx public key: 26b01cb226c6f6a76bd72de51cf91822cf5b3f2c109789676cce5a2c15dac1a6
Timestamp: 1717586281 Timestamp [UCT]: 2024-06-05 11:18:01 Age [y:d:h:m:s]: 00:234:06:13:22
Block: 1037555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167600 RingCT/type: yes/0
Extra: 0126b01cb226c6f6a76bd72de51cf91822cf5b3f2c109789676cce5a2c15dac1a602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: faaa4de939a55c850cb5ecc814f43f12199120188b5ed871a75fe80d07ee7934 0.600000000000 1506100 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": 1037565, "vin": [ { "gen": { "height": 1037555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "faaa4de939a55c850cb5ecc814f43f12199120188b5ed871a75fe80d07ee7934" } } ], "extra": [ 1, 38, 176, 28, 178, 38, 198, 246, 167, 107, 215, 45, 229, 28, 249, 24, 34, 207, 91, 63, 44, 16, 151, 137, 103, 108, 206, 90, 44, 21, 218, 193, 166, 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