Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3ff019a5d0a7af4bb056ca8682601cf6b6f2e7c73540b455b81bda8f5bad2c5

Tx prefix hash: 16d80b1bab4abdbd0c73d5bd36d6717772394c02c33fd39501d05ff42516e1f6
Tx public key: 8ca41aae1acc9b564277960ed78e74ce73d22c4d612da938b81a5752ac28f2fe
Timestamp: 1730574836 Timestamp [UCT]: 2024-11-02 19:13:56 Age [y:d:h:m:s]: 01:011:14:45:06
Block: 1145142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266728 RingCT/type: yes/0
Extra: 018ca41aae1acc9b564277960ed78e74ce73d22c4d612da938b81a5752ac28f2fe021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53e03dad9ece39f359c43ac54424846323d30c4a8993ba305ea13ca56df0ae1b 0.600000000000 1629537 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": 1145152, "vin": [ { "gen": { "height": 1145142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53e03dad9ece39f359c43ac54424846323d30c4a8993ba305ea13ca56df0ae1b" } } ], "extra": [ 1, 140, 164, 26, 174, 26, 204, 155, 86, 66, 119, 150, 14, 215, 142, 116, 206, 115, 210, 44, 77, 97, 45, 169, 56, 184, 26, 87, 82, 172, 40, 242, 254, 2, 17, 0, 0, 0, 8, 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