Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4251da92dbfd14950e8747b552d74a567aab4cf58308354b5f46143b9a8495e

Tx prefix hash: 775bcaa8b7dfabce9474b73e549f3bd6703dd969475c54c6cd924d65c7720611
Tx public key: c72c9586408ba99073de1649f10ec2e08aac053c8b3eac7e3d732b914f8c34d8
Timestamp: 1725123387 Timestamp [UCT]: 2024-08-31 16:56:27 Age [y:d:h:m:s]: 01:074:11:49:31
Block: 1100031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311681 RingCT/type: yes/0
Extra: 01c72c9586408ba99073de1649f10ec2e08aac053c8b3eac7e3d732b914f8c34d8021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a827ed4a0e4ab2046ed5c15da13540713255d245f4057240be0f0e29ff07e45 0.600000000000 1576002 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": 1100041, "vin": [ { "gen": { "height": 1100031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a827ed4a0e4ab2046ed5c15da13540713255d245f4057240be0f0e29ff07e45" } } ], "extra": [ 1, 199, 44, 149, 134, 64, 139, 169, 144, 115, 222, 22, 73, 241, 14, 194, 224, 138, 172, 5, 60, 139, 62, 172, 126, 61, 115, 43, 145, 79, 140, 52, 216, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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