Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33fd601fc086bfbe98ef338373ae89e2359c0f48f8a2f97653edc001a16e899e

Tx prefix hash: eee084aaebf6e1428063d10fd3eb0688d305c8a72056711813ab438f47a3151c
Tx public key: 5c5c741f4a78ad31c5c91cc662c3442ad0dd3a992c0c70bf8b8e0bf25481a8e4
Timestamp: 1587536434 Timestamp [UCT]: 2020-04-22 06:20:34 Age [y:d:h:m:s]: 04:247:23:54:36
Block: 94974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1087716 RingCT/type: yes/0
Extra: 015c5c741f4a78ad31c5c91cc662c3442ad0dd3a992c0c70bf8b8e0bf25481a8e4021100000132209b4bc8000000000000000000

1 output(s) for total of 297.380495445000 dcy

stealth address amount amount idx
00: a4773598dcee3b873ff6e40970a9b53441f2e8c5924e77bce403a4142212d8a8 297.380495445000 168860 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": 94984, "vin": [ { "gen": { "height": 94974 } } ], "vout": [ { "amount": 297380495445, "target": { "key": "a4773598dcee3b873ff6e40970a9b53441f2e8c5924e77bce403a4142212d8a8" } } ], "extra": [ 1, 92, 92, 116, 31, 74, 120, 173, 49, 197, 201, 28, 198, 98, 195, 68, 42, 208, 221, 58, 153, 44, 12, 112, 191, 139, 142, 11, 242, 84, 129, 168, 228, 2, 17, 0, 0, 1, 50, 32, 155, 75, 200, 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