Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77ce99ad503c7c2134e01e0c60d05f98fb7f2dc51feadb68881749e4f0fcac57

Tx prefix hash: e86854c58b789f87350c5e5237ac7bf5ddcb5dfe6436dd54749877aa4d72e802
Tx public key: 36739176e927b613afcc7f3decc054a3d3ba1141fbd40479e4f146f520686f24
Timestamp: 1639325681 Timestamp [UCT]: 2021-12-12 16:14:41 Age [y:d:h:m:s]: 03:095:10:34:00
Block: 394017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 846956 RingCT/type: yes/0
Extra: 0136739176e927b613afcc7f3decc054a3d3ba1141fbd40479e4f146f520686f24021100000001408d5ef5000000000000000000

1 output(s) for total of 30.370956863000 dcy

stealth address amount amount idx
00: a9bec627880f7ba99548b4c4a15d2779b40976af9e53fb085d7eeb1ca902b818 30.370956863000 791454 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": 394027, "vin": [ { "gen": { "height": 394017 } } ], "vout": [ { "amount": 30370956863, "target": { "key": "a9bec627880f7ba99548b4c4a15d2779b40976af9e53fb085d7eeb1ca902b818" } } ], "extra": [ 1, 54, 115, 145, 118, 233, 39, 182, 19, 175, 204, 127, 61, 236, 192, 84, 163, 211, 186, 17, 65, 251, 212, 4, 121, 228, 241, 70, 245, 32, 104, 111, 36, 2, 17, 0, 0, 0, 1, 64, 141, 94, 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