Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef7b9152cac3e400d92dabf5fee7100e3b40573070acee2d16d975bc58e4e8d8

Tx prefix hash: f50b43713331a48460affc5967e7879227f20bc817e2f4f36f9226ccf2596c66
Tx public key: 494c815283ca513e30029a6d37a5a40ea0da92f4a3e2a4348b5c98fe900ca5bc
Timestamp: 1681531177 Timestamp [UCT]: 2023-04-15 03:59:37 Age [y:d:h:m:s]: 01:220:08:38:48
Block: 738868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418952 RingCT/type: yes/0
Extra: 01494c815283ca513e30029a6d37a5a40ea0da92f4a3e2a4348b5c98fe900ca5bc0211000000025029cbac000000000000000000

1 output(s) for total of 2.186954280000 dcy

stealth address amount amount idx
00: 6b5c9d112afa3bb145a56a84aca17b375579c93e45d06954aefcafd2d0e0e8e1 2.186954280000 1185637 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": 738878, "vin": [ { "gen": { "height": 738868 } } ], "vout": [ { "amount": 2186954280, "target": { "key": "6b5c9d112afa3bb145a56a84aca17b375579c93e45d06954aefcafd2d0e0e8e1" } } ], "extra": [ 1, 73, 76, 129, 82, 131, 202, 81, 62, 48, 2, 154, 109, 55, 165, 164, 14, 160, 218, 146, 244, 163, 226, 164, 52, 139, 92, 152, 254, 144, 12, 165, 188, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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