Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60921aabcc6ac067b2d6c69e47d4c96aff759663ac8747338c1e6ecf625693d2

Tx prefix hash: 4babbecbe59a17a59a095c8a7a750c7a471c73d1a428425de1de7f92c63e95a0
Tx public key: 7790730e4e06c015fd3308d71f8c0bf2ff7346cb68c8ff0642a8da4c59dc2b1e
Timestamp: 1577522325 Timestamp [UCT]: 2019-12-28 08:38:45 Age [y:d:h:m:s]: 04:247:02:39:28
Block: 33285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1065862 RingCT/type: yes/0
Extra: 017790730e4e06c015fd3308d71f8c0bf2ff7346cb68c8ff0642a8da4c59dc2b1e02110000000dd81c26c0000000000000000000

1 output(s) for total of 476.117160887000 dcy

stealth address amount amount idx
00: 17303edecdc539cd7141957b4ae05245fc452f91203d2b0e6c72780e2d5aca3e 476.117160887000 55704 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": 33295, "vin": [ { "gen": { "height": 33285 } } ], "vout": [ { "amount": 476117160887, "target": { "key": "17303edecdc539cd7141957b4ae05245fc452f91203d2b0e6c72780e2d5aca3e" } } ], "extra": [ 1, 119, 144, 115, 14, 78, 6, 192, 21, 253, 51, 8, 215, 31, 140, 11, 242, 255, 115, 70, 203, 104, 200, 255, 6, 66, 168, 218, 76, 89, 220, 43, 30, 2, 17, 0, 0, 0, 13, 216, 28, 38, 192, 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