Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5a2e3b6956b06de7ba8dd9d67db99d6ba435450076fd5667666a5badfc660bd

Tx prefix hash: f0e916e548e0d6fab51e84358d4628a96ff66de3c5e00297494f791a6c57abf9
Tx public key: 9230ac613e9cacb622c85909ee58583b314d59c62c4041bf2dcc2c14aacc3b62
Timestamp: 1686353133 Timestamp [UCT]: 2023-06-09 23:25:33 Age [y:d:h:m:s]: 02:178:03:37:01
Block: 778866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 647114 RingCT/type: yes/0
Extra: 019230ac613e9cacb622c85909ee58583b314d59c62c4041bf2dcc2c14aacc3b62021100000001e6d27f9c000000000000000000

1 output(s) for total of 1.611735531000 dcy

stealth address amount amount idx
00: 125dba07ecc5916e72effe5992a5cf9ea6f03ddf3a7391e611d41014f63e2383 1.611735531000 1228509 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": 778876, "vin": [ { "gen": { "height": 778866 } } ], "vout": [ { "amount": 1611735531, "target": { "key": "125dba07ecc5916e72effe5992a5cf9ea6f03ddf3a7391e611d41014f63e2383" } } ], "extra": [ 1, 146, 48, 172, 97, 62, 156, 172, 182, 34, 200, 89, 9, 238, 88, 88, 59, 49, 77, 89, 198, 44, 64, 65, 191, 45, 204, 44, 20, 170, 204, 59, 98, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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