Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbfb63a1d287ac5a0b3c33cd1ebecf337be218ba2ce6587f7ee1942690494846

Tx prefix hash: ce49cb12b1dde92915fa6404458d108235086e89df18442b23fa9a234a57a27b
Tx public key: 0c798a6c7525fb223d576a566a3efb7f977d0e71a09c59f1090ca85781a3b2cc
Timestamp: 1723862562 Timestamp [UCT]: 2024-08-17 02:42:42 Age [y:d:h:m:s]: 00:302:05:36:08
Block: 1089575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215839 RingCT/type: yes/0
Extra: 010c798a6c7525fb223d576a566a3efb7f977d0e71a09c59f1090ca85781a3b2cc02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a28e91ef0c0fc6a294b8f5ceb1d0306383e2afae3e696236d9f3fd3f2f4e2f4 0.600000000000 1564198 of 15

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": 1089585, "vin": [ { "gen": { "height": 1089575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a28e91ef0c0fc6a294b8f5ceb1d0306383e2afae3e696236d9f3fd3f2f4e2f4" } } ], "extra": [ 1, 12, 121, 138, 108, 117, 37, 251, 34, 61, 87, 106, 86, 106, 62, 251, 127, 151, 125, 14, 113, 160, 156, 89, 241, 9, 12, 168, 87, 129, 163, 178, 204, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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