Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c710c889bb9ea5fc075bc6cc699f1f7eefc92f89ce63b678c8681b001e86ed1d

Tx prefix hash: b51c95cd89fd3f5c6409b305c73e1bced74d9da6226eefa8c3bda2101e47102d
Tx public key: 317b08736533c613458c81b369365d0c633f83d8880ddd908608eb94e2f4c5fd
Timestamp: 1735510686 Timestamp [UCT]: 2024-12-29 22:18:06 Age [y:d:h:m:s]: 00:097:18:45:44
Block: 1186007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69671 RingCT/type: yes/0
Extra: 01317b08736533c613458c81b369365d0c633f83d8880ddd908608eb94e2f4c5fd021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65be54b66e7756ef3db87f06b5f1e1be0c21b8954ff2626661e47a51ab39b0b1 0.600000000000 1672482 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": 1186017, "vin": [ { "gen": { "height": 1186007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65be54b66e7756ef3db87f06b5f1e1be0c21b8954ff2626661e47a51ab39b0b1" } } ], "extra": [ 1, 49, 123, 8, 115, 101, 51, 198, 19, 69, 140, 129, 179, 105, 54, 93, 12, 99, 63, 131, 216, 136, 13, 221, 144, 134, 8, 235, 148, 226, 244, 197, 253, 2, 17, 0, 0, 0, 3, 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