Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 825e94cfe530d695e2c5624c4fd89ad03dee24a3966fa560a34a77a16894c60f

Tx prefix hash: f75f23719b9210fd8011721195028f7bf27462aaee2d60088e27e8353677f67d
Tx public key: 825fa9cd09b664734099db7d0e308c20d2af0f21d7f0595e764d5ecd4becfc34
Timestamp: 1677787154 Timestamp [UCT]: 2023-03-02 19:59:14 Age [y:d:h:m:s]: 01:360:08:04:55
Block: 708476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518202 RingCT/type: yes/0
Extra: 01825fa9cd09b664734099db7d0e308c20d2af0f21d7f0595e764d5ecd4becfc34021100000001835e4d22000000000000000000

1 output(s) for total of 2.757558982000 dcy

stealth address amount amount idx
00: 5106cb7a3838d3ae7ae2f60ce4ec5ed3f17edd3150aa8b50d8e01282db376fc8 2.757558982000 1152371 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": 708486, "vin": [ { "gen": { "height": 708476 } } ], "vout": [ { "amount": 2757558982, "target": { "key": "5106cb7a3838d3ae7ae2f60ce4ec5ed3f17edd3150aa8b50d8e01282db376fc8" } } ], "extra": [ 1, 130, 95, 169, 205, 9, 182, 100, 115, 64, 153, 219, 125, 14, 48, 140, 32, 210, 175, 15, 33, 215, 240, 89, 94, 118, 77, 94, 205, 75, 236, 252, 52, 2, 17, 0, 0, 0, 1, 131, 94, 77, 34, 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