Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 986a883010e2c85b3a7f922ca6b50531f0d7e6c182f70b3ee4656f8f0817425b

Tx prefix hash: a33d087bae840663ecb9a399bae1f51eb84fb93dbdb74459a920f1fe73d1f40b
Tx public key: 665c710d0b410df8b29d46354e2134cda951723dbacc4999a767bc9009ebf6b5
Timestamp: 1729148990 Timestamp [UCT]: 2024-10-17 07:09:50 Age [y:d:h:m:s]: 00:148:17:50:06
Block: 1133402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106099 RingCT/type: yes/0
Extra: 01665c710d0b410df8b29d46354e2134cda951723dbacc4999a767bc9009ebf6b502110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4293008b8deee52fe3128617ecee1ba4be05409545f963f0f11d94f788c57bd2 0.600000000000 1616515 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": 1133412, "vin": [ { "gen": { "height": 1133402 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4293008b8deee52fe3128617ecee1ba4be05409545f963f0f11d94f788c57bd2" } } ], "extra": [ 1, 102, 92, 113, 13, 11, 65, 13, 248, 178, 157, 70, 53, 78, 33, 52, 205, 169, 81, 114, 61, 186, 204, 73, 153, 167, 103, 188, 144, 9, 235, 246, 181, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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