Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bedd80fd88e1a92866e79d2cf0890e9b73057d97d75b1c67cf2dce5a9f6d7f47

Tx prefix hash: 297250e59754ce089257d33373fccd5f14c09aac1cb2e708687a422bb4a32e25
Tx public key: 37bcc08e2855af19cf6fc1b6d6b15a86657739f68aa5eb6b5265c94bf8def0e2
Timestamp: 1718025593 Timestamp [UCT]: 2024-06-10 13:19:53 Age [y:d:h:m:s]: 00:279:02:34:49
Block: 1041189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199464 RingCT/type: yes/0
Extra: 0137bcc08e2855af19cf6fc1b6d6b15a86657739f68aa5eb6b5265c94bf8def0e202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81ef39cf83ba4cad0f9a7a08458a2eabb6db18edbdb85e60a688dddce0093b5f 0.600000000000 1509854 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": 1041199, "vin": [ { "gen": { "height": 1041189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81ef39cf83ba4cad0f9a7a08458a2eabb6db18edbdb85e60a688dddce0093b5f" } } ], "extra": [ 1, 55, 188, 192, 142, 40, 85, 175, 25, 207, 111, 193, 182, 214, 177, 90, 134, 101, 119, 57, 246, 138, 165, 235, 107, 82, 101, 201, 75, 248, 222, 240, 226, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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