Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 633efd6c7cb23f9eb0d1a258a587e39ec630591f9e906c6e267c6ce9602d2f3b

Tx prefix hash: 6758624e473cf89251fdd108e72a9fe64b34c38d8a505befb92dcbe7cf28492b
Tx public key: 4659a7d5fb6a3a1fde1a912061c0d0cc79d99b117cdb3f21329a4dfd1ad90592
Timestamp: 1711551789 Timestamp [UCT]: 2024-03-27 15:03:09 Age [y:d:h:m:s]: 01:239:08:19:48
Block: 987541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429732 RingCT/type: yes/0
Extra: 014659a7d5fb6a3a1fde1a912061c0d0cc79d99b117cdb3f21329a4dfd1ad905920211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61decc58e5cc243e12303740db1be3b08b183e22b43445f27be629c5f24d68e4 0.600000000000 1447792 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": 987551, "vin": [ { "gen": { "height": 987541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61decc58e5cc243e12303740db1be3b08b183e22b43445f27be629c5f24d68e4" } } ], "extra": [ 1, 70, 89, 167, 213, 251, 106, 58, 31, 222, 26, 145, 32, 97, 192, 208, 204, 121, 217, 155, 17, 124, 219, 63, 33, 50, 154, 77, 253, 26, 217, 5, 146, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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