Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 486f4f48455d495f5bcce3cb7f20a998e168ffcb1d6a99ccba1d14f119d7f9b0

Tx prefix hash: 35c0d45e5a215f8452295ee77f9db790f8f23fd70245de0934ce51e1d96d13a8
Tx public key: 2b266b9477b318090ace2c75324c94fcb4080664ae007eed1a31f8ccde4aea4a
Timestamp: 1663715178 Timestamp [UCT]: 2022-09-20 23:06:18 Age [y:d:h:m:s]: 03:041:09:56:50
Block: 592254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 809574 RingCT/type: yes/0
Extra: 012b266b9477b318090ace2c75324c94fcb4080664ae007eed1a31f8ccde4aea4a02110000000175e3f0e9000000000000000000

1 output(s) for total of 6.692936626000 dcy

stealth address amount amount idx
00: 5e2d7745af1e3372f3bd6e24b053b9d80d2da294944cc41cbcf97e51bae6bfb0 6.692936626000 1026901 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": 592264, "vin": [ { "gen": { "height": 592254 } } ], "vout": [ { "amount": 6692936626, "target": { "key": "5e2d7745af1e3372f3bd6e24b053b9d80d2da294944cc41cbcf97e51bae6bfb0" } } ], "extra": [ 1, 43, 38, 107, 148, 119, 179, 24, 9, 10, 206, 44, 117, 50, 76, 148, 252, 180, 8, 6, 100, 174, 0, 126, 237, 26, 49, 248, 204, 222, 74, 234, 74, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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