Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a59cc2bd31cd4ea56a2dbf3989c99eae9e682a6c3f1e97bd49b69fe2fb01486

Tx prefix hash: d14e54251f29b7e4c2b79b9dc071b90f283cced154d757da6c08b4fcc0feb076
Tx public key: dc95f8446f16811400e387682566cb214df36bd533e3457d43736255a98e2be3
Timestamp: 1681506213 Timestamp [UCT]: 2023-04-14 21:03:33 Age [y:d:h:m:s]: 01:359:05:24:49
Block: 738657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518009 RingCT/type: yes/0
Extra: 01dc95f8446f16811400e387682566cb214df36bd533e3457d43736255a98e2be3021100000003b3164c24000000000000000000

1 output(s) for total of 2.190397563000 dcy

stealth address amount amount idx
00: 963eff70d4f93957d9db828f25875540298acc5d8a1a257b514151e279cd9119 2.190397563000 1185390 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": 738667, "vin": [ { "gen": { "height": 738657 } } ], "vout": [ { "amount": 2190397563, "target": { "key": "963eff70d4f93957d9db828f25875540298acc5d8a1a257b514151e279cd9119" } } ], "extra": [ 1, 220, 149, 248, 68, 111, 22, 129, 20, 0, 227, 135, 104, 37, 102, 203, 33, 77, 243, 107, 213, 51, 227, 69, 125, 67, 115, 98, 85, 169, 142, 43, 227, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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