Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9d29231db917e0c6870ff6b4bdeba77bbda7ac859f6508192246174fc06755a

Tx prefix hash: a794853371f8650187e75af2d4b506d6a90e4635d57d3560926a237bcb05a532
Tx public key: 79af1cb2af004c1f6e8f836c0e8e0eb216afd52e30d0dc11bbe5256637162e06
Timestamp: 1730411193 Timestamp [UCT]: 2024-10-31 21:46:33 Age [y:d:h:m:s]: 00:152:12:49:45
Block: 1143789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108848 RingCT/type: yes/0
Extra: 0179af1cb2af004c1f6e8f836c0e8e0eb216afd52e30d0dc11bbe5256637162e06021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8d64aa4231323837f92a8e8ffd4d7290d0fa1f12e8ea86cbeb687037a5dce98 0.600000000000 1627782 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": 1143799, "vin": [ { "gen": { "height": 1143789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8d64aa4231323837f92a8e8ffd4d7290d0fa1f12e8ea86cbeb687037a5dce98" } } ], "extra": [ 1, 121, 175, 28, 178, 175, 0, 76, 31, 110, 143, 131, 108, 14, 142, 14, 178, 22, 175, 213, 46, 48, 208, 220, 17, 187, 229, 37, 102, 55, 22, 46, 6, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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