Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac21534d38c1b8a38dc15c6989aa8d6fc27a9520fbde50bbba6c60fa79051524

Tx prefix hash: 2c340aa2ebd3548884a4130d076ee2ec311a7be109213c5857b36312e45e9761
Tx public key: bd0c2e10c221ca7688250682c3c36dac3ea16eaac0255f8162bca54887ea933c
Timestamp: 1736621679 Timestamp [UCT]: 2025-01-11 18:54:39 Age [y:d:h:m:s]: 00:160:01:28:22
Block: 1195213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114059 RingCT/type: yes/0
Extra: 01bd0c2e10c221ca7688250682c3c36dac3ea16eaac0255f8162bca54887ea933c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64299eb9ca0b457a71600a3f3c7412ac35cf54f52e9a49672f51cbab289b042a 0.600000000000 1681802 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": 1195223, "vin": [ { "gen": { "height": 1195213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64299eb9ca0b457a71600a3f3c7412ac35cf54f52e9a49672f51cbab289b042a" } } ], "extra": [ 1, 189, 12, 46, 16, 194, 33, 202, 118, 136, 37, 6, 130, 195, 195, 109, 172, 62, 161, 110, 170, 192, 37, 95, 129, 98, 188, 165, 72, 135, 234, 147, 60, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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