Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4003d9c2cf080ea0ddff7496d5ee8e7d37049e9aef63c5b24b1fb24eb1af879

Tx prefix hash: da41754d69c73518f6bb395d405844fd4c9558c43770051f693ee7faac7f15b0
Tx public key: c8c8025ae27b7d68c39d6353a28e196f00902803aa4f811a4d4d28430e6455fc
Timestamp: 1681002465 Timestamp [UCT]: 2023-04-09 01:07:45 Age [y:d:h:m:s]: 02:001:15:06:50
Block: 734544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523264 RingCT/type: yes/0
Extra: 01c8c8025ae27b7d68c39d6353a28e196f00902803aa4f811a4d4d28430e6455fc021100000005b3164c24000000000000000000

1 output(s) for total of 2.260221647000 dcy

stealth address amount amount idx
00: 04bda7b56e8948027b49e05c135a9fb51c21c5b305e753c5c19cf8b0c9ad987e 2.260221647000 1180765 of 0

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": 734554, "vin": [ { "gen": { "height": 734544 } } ], "vout": [ { "amount": 2260221647, "target": { "key": "04bda7b56e8948027b49e05c135a9fb51c21c5b305e753c5c19cf8b0c9ad987e" } } ], "extra": [ 1, 200, 200, 2, 90, 226, 123, 125, 104, 195, 157, 99, 83, 162, 142, 25, 111, 0, 144, 40, 3, 170, 79, 129, 26, 77, 77, 40, 67, 14, 100, 85, 252, 2, 17, 0, 0, 0, 5, 179, 22, 76, 36, 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