Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c014b661c27494c945a5cc8bf64880243f7c17456a47746f53079b135a5c209b

Tx prefix hash: 3099d5f60e74d461967ef36b84063cc96effc8548f8d0b1c5b1f0a5cfbfec74b
Tx public key: a1a65d33340fa41f9d5954d2888609d8fd823af04ec4acb3063a6a506950096b
Timestamp: 1705241833 Timestamp [UCT]: 2024-01-14 14:17:13 Age [y:d:h:m:s]: 01:105:18:40:12
Block: 935196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336717 RingCT/type: yes/0
Extra: 01a1a65d33340fa41f9d5954d2888609d8fd823af04ec4acb3063a6a506950096b0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bde4a23b5897b0132b95b2ffe5b3750599a0907a489e23f96e7681e64b33300c 0.600000000000 1393212 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": 935206, "vin": [ { "gen": { "height": 935196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bde4a23b5897b0132b95b2ffe5b3750599a0907a489e23f96e7681e64b33300c" } } ], "extra": [ 1, 161, 166, 93, 51, 52, 15, 164, 31, 157, 89, 84, 210, 136, 134, 9, 216, 253, 130, 58, 240, 78, 196, 172, 179, 6, 58, 106, 80, 105, 80, 9, 107, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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