Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f46840e6cc400683470e64c94e6ca5381ef344ac64f49896d9635f91dc3e181a

Tx prefix hash: 83718456323006141efc08a5e93b2982272e4249a1b56a14bafb685f7ef3ec36
Tx public key: ea29e0805dbe50dd1dcf17a2e70414ea67add8b1ee730ffb82889771f844f9e8
Timestamp: 1583853461 Timestamp [UCT]: 2020-03-10 15:17:41 Age [y:d:h:m:s]: 05:039:04:00:18
Block: 79859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1183755 RingCT/type: yes/0
Extra: 01ea29e0805dbe50dd1dcf17a2e70414ea67add8b1ee730ffb82889771f844f9e80211000000053b1b9791000000000000000000

1 output(s) for total of 333.735393953000 dcy

stealth address amount amount idx
00: adb60823e53cd56b54946a7902c0c4d60c285221d4a4d014d7510a71a9f24f70 333.735393953000 146121 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": 79869, "vin": [ { "gen": { "height": 79859 } } ], "vout": [ { "amount": 333735393953, "target": { "key": "adb60823e53cd56b54946a7902c0c4d60c285221d4a4d014d7510a71a9f24f70" } } ], "extra": [ 1, 234, 41, 224, 128, 93, 190, 80, 221, 29, 207, 23, 162, 231, 4, 20, 234, 103, 173, 216, 177, 238, 115, 15, 251, 130, 136, 151, 113, 248, 68, 249, 232, 2, 17, 0, 0, 0, 5, 59, 27, 151, 145, 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