Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61ea814cbf585dee1aefd138b9a1345d32451806157ca74e0407a2aedbf5c30e

Tx prefix hash: 1ab01af2da16b6aef12c8482c5b36a9d2608a11cc0e952278960191a10a27b7d
Tx public key: 960169d524c895be1c7f96ad1814d4ae33f2d0a58ef81e6499b03bc63db003d6
Timestamp: 1609181285 Timestamp [UCT]: 2020-12-28 18:48:05 Age [y:d:h:m:s]: 04:000:03:31:58
Block: 171004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1013576 RingCT/type: yes/0
Extra: 01960169d524c895be1c7f96ad1814d4ae33f2d0a58ef81e6499b03bc63db003d60211000002224ea414e5000000000000000000

1 output(s) for total of 166.503541023000 dcy

stealth address amount amount idx
00: e349597176ee93540c2a136558f17dce81b34f73f1ae105380b7170c990511c4 166.503541023000 321431 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": 171014, "vin": [ { "gen": { "height": 171004 } } ], "vout": [ { "amount": 166503541023, "target": { "key": "e349597176ee93540c2a136558f17dce81b34f73f1ae105380b7170c990511c4" } } ], "extra": [ 1, 150, 1, 105, 213, 36, 200, 149, 190, 28, 127, 150, 173, 24, 20, 212, 174, 51, 242, 208, 165, 142, 248, 30, 100, 153, 176, 59, 198, 61, 176, 3, 214, 2, 17, 0, 0, 2, 34, 78, 164, 20, 229, 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