Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d83fb7482b3abdee1be163ff18301cbb604433f53ba8d94cbceb632973d9d957

Tx prefix hash: b1c6c4497313c7d792d74df0c41b2afe5ade9878a0aa0b22db6bb7f76f79f6fd
Tx public key: 7f7d05937bd525bfe8fda24c19844fdd8b01715192792a3b81286b980b17e65f
Timestamp: 1715512877 Timestamp [UCT]: 2024-05-12 11:21:17 Age [y:d:h:m:s]: 00:320:18:40:04
Block: 1020393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229248 RingCT/type: yes/0
Extra: 017f7d05937bd525bfe8fda24c19844fdd8b01715192792a3b81286b980b17e65f02110000000941ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6111becbe7713245c2adf4fed1e5847727176e1dddf8f8297d7da9e25989a2b2 0.600000000000 1484458 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": 1020403, "vin": [ { "gen": { "height": 1020393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6111becbe7713245c2adf4fed1e5847727176e1dddf8f8297d7da9e25989a2b2" } } ], "extra": [ 1, 127, 125, 5, 147, 123, 213, 37, 191, 232, 253, 162, 76, 25, 132, 79, 221, 139, 1, 113, 81, 146, 121, 42, 59, 129, 40, 107, 152, 11, 23, 230, 95, 2, 17, 0, 0, 0, 9, 65, 238, 28, 155, 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