Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b18646cbc1fa1c560b6b9927f6b89965be66cda4a5a2488dcf8af9f0bfd0390f

Tx prefix hash: 159013c928a3e5df77ed582401449374fc907daf92b52b8b3ac2d883377a4a5a
Tx public key: 55b86579c94ddc0f439e2bf6bdd49be4bb35941b6c1433b3c3f1211462aeef41
Timestamp: 1755189233 Timestamp [UCT]: 2025-08-14 16:33:53 Age [y:d:h:m:s]: 00:052:08:43:25
Block: 1346762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36913 RingCT/type: yes/0
Extra: 0155b86579c94ddc0f439e2bf6bdd49be4bb35941b6c1433b3c3f1211462aeef410211000000048368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6f0bc2df7c8dfea4b260c0e0abbed45bd0241b37f9130e4915394f71201c2e3 0.600000000000 1834667 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": 1346772, "vin": [ { "gen": { "height": 1346762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6f0bc2df7c8dfea4b260c0e0abbed45bd0241b37f9130e4915394f71201c2e3" } } ], "extra": [ 1, 85, 184, 101, 121, 201, 77, 220, 15, 67, 158, 43, 246, 189, 212, 155, 228, 187, 53, 148, 27, 108, 20, 51, 179, 195, 241, 33, 20, 98, 174, 239, 65, 2, 17, 0, 0, 0, 4, 131, 104, 38, 109, 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