Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b14c20a92889873f6b93bcf486927fadf0d7bbce47605f3803de6e76c8367bb6

Tx prefix hash: 21464928424c67851d64b837f7789aa646b6959a6b28aeae87375f3943d4b2d5
Tx public key: cefc9b1300c590c18a027837a19f1c7f76d689a8e3807de6aae63009c261bcc6
Timestamp: 1723379944 Timestamp [UCT]: 2024-08-11 12:39:04 Age [y:d:h:m:s]: 01:096:06:24:47
Block: 1085581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327273 RingCT/type: yes/0
Extra: 01cefc9b1300c590c18a027837a19f1c7f76d689a8e3807de6aae63009c261bcc6021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 358ffabe89a33d80a4413b8d483f4a813ce70ff70a31a0528d1b9c7f279a8d27 0.600000000000 1560168 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": 1085591, "vin": [ { "gen": { "height": 1085581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "358ffabe89a33d80a4413b8d483f4a813ce70ff70a31a0528d1b9c7f279a8d27" } } ], "extra": [ 1, 206, 252, 155, 19, 0, 197, 144, 193, 138, 2, 120, 55, 161, 159, 28, 127, 118, 214, 137, 168, 227, 128, 125, 230, 170, 230, 48, 9, 194, 97, 188, 198, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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