Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e227a16fd706fb5615d8430b2afe91bc0bd911492a5cb122c9d035dffd24cfc

Tx prefix hash: 572e41135bfb2114c5251857f72bd01dae4949b6712c06d4324af0a7c00a15f7
Tx public key: 06ba3b28451856390f15ad3d83be8b94148d390d983f22fa9ac0e2648d016bd1
Timestamp: 1721220142 Timestamp [UCT]: 2024-07-17 12:42:22 Age [y:d:h:m:s]: 00:251:12:06:58
Block: 1067683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179635 RingCT/type: yes/0
Extra: 0106ba3b28451856390f15ad3d83be8b94148d390d983f22fa9ac0e2648d016bd102110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1066e7ac49c477fb83f02b3aa64351ea5df51d2c4d9b275d850d6cf7efa43cd3 0.600000000000 1538560 of 15

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": 1067693, "vin": [ { "gen": { "height": 1067683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1066e7ac49c477fb83f02b3aa64351ea5df51d2c4d9b275d850d6cf7efa43cd3" } } ], "extra": [ 1, 6, 186, 59, 40, 69, 24, 86, 57, 15, 21, 173, 61, 131, 190, 139, 148, 20, 141, 57, 13, 152, 63, 34, 250, 154, 192, 226, 100, 141, 1, 107, 209, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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