Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 439141b95182aaad2f08f4df3e50679c3ab2d299b8687d4780e05c8c80a4943b

Tx prefix hash: 9faf3e5fea261d1e99fb8d79afb3a06bced1a393e071f3b2c22ba9bc2ae7e12c
Tx public key: 0863ea269eb09fbd9e38b39ed852389b2dd8545b0cb668c9fe5101946e444dfe
Timestamp: 1700974027 Timestamp [UCT]: 2023-11-26 04:47:07 Age [y:d:h:m:s]: 01:203:05:07:38
Block: 899809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406352 RingCT/type: yes/0
Extra: 010863ea269eb09fbd9e38b39ed852389b2dd8545b0cb668c9fe5101946e444dfe02110000000433af99f4000000000000000000

1 output(s) for total of 0.640559148000 dcy

stealth address amount amount idx
00: df3d4cc2a3c55b68bad996d7fe3969662b6ba6e882b9ecd533a347c1df8c22fa 0.640559148000 1356274 of 0

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": 899819, "vin": [ { "gen": { "height": 899809 } } ], "vout": [ { "amount": 640559148, "target": { "key": "df3d4cc2a3c55b68bad996d7fe3969662b6ba6e882b9ecd533a347c1df8c22fa" } } ], "extra": [ 1, 8, 99, 234, 38, 158, 176, 159, 189, 158, 56, 179, 158, 216, 82, 56, 155, 45, 216, 84, 91, 12, 182, 104, 201, 254, 81, 1, 148, 110, 68, 77, 254, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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