Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eed210afbda4c9c6cf655f1fdb7f80eada954eb8bd56d28179f006a4797d09e4

Tx prefix hash: f098038001ca07f670886f214b28e1eed20903b7e218d1be1ef9607e7346d40c
Tx public key: ab2c20f6862e4aeb1d81d246b01f44078f75ddb37b2cea7492f8edf1928d2804
Timestamp: 1735253877 Timestamp [UCT]: 2024-12-26 22:57:57 Age [y:d:h:m:s]: 00:170:12:47:55
Block: 1183890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121620 RingCT/type: yes/0
Extra: 01ab2c20f6862e4aeb1d81d246b01f44078f75ddb37b2cea7492f8edf1928d28040211000000141f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79d7f5e106434e735fe95e4e9f4e1baabc3cb8c8cd268ead9df999b95685a745 0.600000000000 1670339 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": 1183900, "vin": [ { "gen": { "height": 1183890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79d7f5e106434e735fe95e4e9f4e1baabc3cb8c8cd268ead9df999b95685a745" } } ], "extra": [ 1, 171, 44, 32, 246, 134, 46, 74, 235, 29, 129, 210, 70, 176, 31, 68, 7, 143, 117, 221, 179, 123, 44, 234, 116, 146, 248, 237, 241, 146, 141, 40, 4, 2, 17, 0, 0, 0, 20, 31, 10, 83, 235, 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