Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7eff141e0e9c5c01b644e11b64cd8df36f341dc91f99115d3e14b87a3b8373a

Tx prefix hash: 5250cfc4437d983348f530937fd7b121ec3ea5bf04e30696ef5b4b8503cee3fd
Tx public key: 2bbeda05d101e457a5ff59f12caf10db2d30330c21d73db016045e701e2cfa79
Timestamp: 1705611262 Timestamp [UCT]: 2024-01-18 20:54:22 Age [y:d:h:m:s]: 01:350:21:53:06
Block: 938247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509692 RingCT/type: yes/0
Extra: 012bbeda05d101e457a5ff59f12caf10db2d30330c21d73db016045e701e2cfa7902110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2748cb463ac576577527274d34bd6ee5de4aa7e5d8a37e6b20ea4f0fcff6de7d 0.600000000000 1396317 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": 938257, "vin": [ { "gen": { "height": 938247 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2748cb463ac576577527274d34bd6ee5de4aa7e5d8a37e6b20ea4f0fcff6de7d" } } ], "extra": [ 1, 43, 190, 218, 5, 209, 1, 228, 87, 165, 255, 89, 241, 44, 175, 16, 219, 45, 48, 51, 12, 33, 215, 61, 176, 22, 4, 94, 112, 30, 44, 250, 121, 2, 17, 0, 0, 0, 4, 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