Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14745c50daa0e1f991f07f5fe65e174fd207d8b13afdb645b858b3420d68d40b

Tx prefix hash: a347d81911158d586d8acb3e48a8789fd1805816c7d3051a21b4d937d21420d3
Tx public key: ce3306c4eef244388e7f67067b74157094107be73802cd0bdc72d93cb012e51d
Timestamp: 1696320018 Timestamp [UCT]: 2023-10-03 08:00:18 Age [y:d:h:m:s]: 01:258:22:39:12
Block: 861443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446028 RingCT/type: yes/0
Extra: 01ce3306c4eef244388e7f67067b74157094107be73802cd0bdc72d93cb012e51d021100000005faf35c9c000000000000000000

1 output(s) for total of 0.858384326000 dcy

stealth address amount amount idx
00: e40d70c2b7bd4a66e35fff8619dd2a455503d4e9b804a73826d3cc884d047d27 0.858384326000 1315785 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": 861453, "vin": [ { "gen": { "height": 861443 } } ], "vout": [ { "amount": 858384326, "target": { "key": "e40d70c2b7bd4a66e35fff8619dd2a455503d4e9b804a73826d3cc884d047d27" } } ], "extra": [ 1, 206, 51, 6, 196, 238, 242, 68, 56, 142, 127, 103, 6, 123, 116, 21, 112, 148, 16, 123, 231, 56, 2, 205, 11, 220, 114, 217, 60, 176, 18, 229, 29, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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