Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87154c517a094ee7806e92b8280fdb198551400a878e772a114d359f64fb696a

Tx prefix hash: 3ec7fcda6cb1516046a07ca4d7f82fb38206714ddb83b6042416ff576e5c71af
Tx public key: 6c66e31b3fb5e4c6c10b3b41dec7a34ad20f028f27c2290c5fbf77bebebfa564
Timestamp: 1694536363 Timestamp [UCT]: 2023-09-12 16:32:43 Age [y:d:h:m:s]: 01:201:03:28:45
Block: 846630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404859 RingCT/type: yes/0
Extra: 016c66e31b3fb5e4c6c10b3b41dec7a34ad20f028f27c2290c5fbf77bebebfa56402110000000475e3f0e9000000000000000000

1 output(s) for total of 0.961088584000 dcy

stealth address amount amount idx
00: f7cc54ab83967b59763c25bcde1c564497589dc1d67afdfd5451162a142b1874 0.961088584000 1300102 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": 846640, "vin": [ { "gen": { "height": 846630 } } ], "vout": [ { "amount": 961088584, "target": { "key": "f7cc54ab83967b59763c25bcde1c564497589dc1d67afdfd5451162a142b1874" } } ], "extra": [ 1, 108, 102, 227, 27, 63, 181, 228, 198, 193, 11, 59, 65, 222, 199, 163, 74, 210, 15, 2, 143, 39, 194, 41, 12, 95, 191, 119, 190, 190, 191, 165, 100, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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