Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4a9850f00ede653c558635d6ad4b249e4eb0f439d53cc941255b0666097ed6b

Tx prefix hash: af0e293f8891678cae2ba4399f50d7916e0e241c76f82eccd613b70898f74e75
Tx public key: 7c44010325e3969ccbb2853f9aea7c75e554e2233d1cee38d91a60d8769fe314
Timestamp: 1577189025 Timestamp [UCT]: 2019-12-24 12:03:45 Age [y:d:h:m:s]: 04:327:13:20:25
Block: 30667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123244 RingCT/type: yes/0
Extra: 017c44010325e3969ccbb2853f9aea7c75e554e2233d1cee38d91a60d8769fe3140211000000504fb58672000000000000000000

1 output(s) for total of 485.722654541000 dcy

stealth address amount amount idx
00: 3ebff556318fbab7f7bcd33f6d32810a7a9fe3369eecf3a63d1bc411ef41fcf2 485.722654541000 50631 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": 30677, "vin": [ { "gen": { "height": 30667 } } ], "vout": [ { "amount": 485722654541, "target": { "key": "3ebff556318fbab7f7bcd33f6d32810a7a9fe3369eecf3a63d1bc411ef41fcf2" } } ], "extra": [ 1, 124, 68, 1, 3, 37, 227, 150, 156, 203, 178, 133, 63, 154, 234, 124, 117, 229, 84, 226, 35, 61, 28, 238, 56, 217, 26, 96, 216, 118, 159, 227, 20, 2, 17, 0, 0, 0, 80, 79, 181, 134, 114, 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