Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10c6a3a533a568a70483f5c35bea97dd53226c46887ea93ed68933396f4abb39

Tx prefix hash: ccc642e3a0dbd4509704437d9bfe722a2d7fc12420dbc62b7c17dfc9243314d2
Tx public key: fdc59f5c037893db631584f1d2dcf59c972a6928627ca14a7672eee5a768a6ff
Timestamp: 1711738624 Timestamp [UCT]: 2024-03-29 18:57:04 Age [y:d:h:m:s]: 01:225:03:07:23
Block: 989089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419568 RingCT/type: yes/0
Extra: 01fdc59f5c037893db631584f1d2dcf59c972a6928627ca14a7672eee5a768a6ff02110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 989f16fe883f403c2ec949eef46de7bd631b0dc22fb4ca22dbb9472741b32ebb 0.600000000000 1449384 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": 989099, "vin": [ { "gen": { "height": 989089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "989f16fe883f403c2ec949eef46de7bd631b0dc22fb4ca22dbb9472741b32ebb" } } ], "extra": [ 1, 253, 197, 159, 92, 3, 120, 147, 219, 99, 21, 132, 241, 210, 220, 245, 156, 151, 42, 105, 40, 98, 124, 161, 74, 118, 114, 238, 229, 167, 104, 166, 255, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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