Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38ac0eb6b1d07bbf868074e48a53508a2176d959db27d1100791c35d10676886

Tx prefix hash: c70d28c676270bf0b6713991f81cd1dea1dd8e169849ee90d4aadd0ecc72d313
Tx public key: 657a8a5ac9a6522075ae7dc2530bdefe13853a4a26286402f56da563e7909454
Timestamp: 1643572353 Timestamp [UCT]: 2022-01-30 19:52:33 Age [y:d:h:m:s]: 03:084:22:36:39
Block: 428700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 839907 RingCT/type: yes/0
Extra: 01657a8a5ac9a6522075ae7dc2530bdefe13853a4a26286402f56da563e7909454021100000002cb8520c2000000000000000000

1 output(s) for total of 23.309837619000 dcy

stealth address amount amount idx
00: 24e3bf4ec91066e3e93addfd6e716c918643af52f0d7ac51838ab5a8e16f8fb2 23.309837619000 838164 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": 428710, "vin": [ { "gen": { "height": 428700 } } ], "vout": [ { "amount": 23309837619, "target": { "key": "24e3bf4ec91066e3e93addfd6e716c918643af52f0d7ac51838ab5a8e16f8fb2" } } ], "extra": [ 1, 101, 122, 138, 90, 201, 166, 82, 32, 117, 174, 125, 194, 83, 11, 222, 254, 19, 133, 58, 74, 38, 40, 100, 2, 245, 109, 165, 99, 231, 144, 148, 84, 2, 17, 0, 0, 0, 2, 203, 133, 32, 194, 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