Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9baf1f447cd29813c15f1b72278f98f71116ac586c787e520d61c07f39b07b92

Tx prefix hash: b848627a21a2c49d4e457fa963d46386da099ac4e99f2deeda320725984b7c08
Tx public key: 6ffc303035f4082e0e502ab2c8881ebe5ce9554c97e3bb1343c9276f01a1a80b
Timestamp: 1704687524 Timestamp [UCT]: 2024-01-08 04:18:44 Age [y:d:h:m:s]: 01:005:06:42:51
Block: 930587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265109 RingCT/type: yes/0
Extra: 016ffc303035f4082e0e502ab2c8881ebe5ce9554c97e3bb1343c9276f01a1a80b02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 240b96a51a6fb13fd8f5d76d6904a20c8e7d0778a7d3ff5a14919cf81327d94f 0.600000000000 1388471 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": 930597, "vin": [ { "gen": { "height": 930587 } } ], "vout": [ { "amount": 600000000, "target": { "key": "240b96a51a6fb13fd8f5d76d6904a20c8e7d0778a7d3ff5a14919cf81327d94f" } } ], "extra": [ 1, 111, 252, 48, 48, 53, 244, 8, 46, 14, 80, 42, 178, 200, 136, 30, 190, 92, 233, 85, 76, 151, 227, 187, 19, 67, 201, 39, 111, 1, 161, 168, 11, 2, 17, 0, 0, 0, 2, 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