Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7602b119cda5619740de1e36b04297a03faa3c5e00f0ab4eb26ae918e02c73f0

Tx prefix hash: 51712ed5ddb719b201c03b2114c9188c746d581316fbbcae80e5d78873c4d365
Tx public key: c32fb2d8ece74d205ed0f80a0291faaa31421ac82c15666803b55a09c48a3420
Timestamp: 1660373806 Timestamp [UCT]: 2022-08-13 06:56:46 Age [y:d:h:m:s]: 02:135:02:19:17
Block: 564775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 618005 RingCT/type: yes/0
Extra: 01c32fb2d8ece74d205ed0f80a0291faaa31421ac82c15666803b55a09c48a3420021100000001ec6d1a1a000000000000000000

1 output(s) for total of 8.254030824000 dcy

stealth address amount amount idx
00: 1ac7669ace53af2cb8a21f58fbce8b9da8f265ea2deb7a60e1c57cb2577b78b1 8.254030824000 997633 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": 564785, "vin": [ { "gen": { "height": 564775 } } ], "vout": [ { "amount": 8254030824, "target": { "key": "1ac7669ace53af2cb8a21f58fbce8b9da8f265ea2deb7a60e1c57cb2577b78b1" } } ], "extra": [ 1, 195, 47, 178, 216, 236, 231, 77, 32, 94, 208, 248, 10, 2, 145, 250, 170, 49, 66, 26, 200, 44, 21, 102, 104, 3, 181, 90, 9, 196, 138, 52, 32, 2, 17, 0, 0, 0, 1, 236, 109, 26, 26, 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