Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b778a0713bfe36be3804abdf83cce23fd65a3a7ae396d524e47e57ca96f9035a

Tx prefix hash: 7343568f23d8f83fbd7c1f0db4e321a31281444486b4959963263b7abe5d7e5a
Tx public key: 48b8d0c611be69ac0619de0a016e7e06fe5e56c67254bff4d7fd349c71227e48
Timestamp: 1708730593 Timestamp [UCT]: 2024-02-23 23:23:13 Age [y:d:h:m:s]: 01:076:20:49:01
Block: 964129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315970 RingCT/type: yes/0
Extra: 0148b8d0c611be69ac0619de0a016e7e06fe5e56c67254bff4d7fd349c71227e4802110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4dabd2122820770e3e6b3fbd15d7949c01c32fe227b592aad20c1832a6f4f70e 0.600000000000 1423856 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": 964139, "vin": [ { "gen": { "height": 964129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4dabd2122820770e3e6b3fbd15d7949c01c32fe227b592aad20c1832a6f4f70e" } } ], "extra": [ 1, 72, 184, 208, 198, 17, 190, 105, 172, 6, 25, 222, 10, 1, 110, 126, 6, 254, 94, 86, 198, 114, 84, 191, 244, 215, 253, 52, 156, 113, 34, 126, 72, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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