Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e340794fab9c5c4804bb31e8899787f14321c5404e217a207852aaccd7e5df8

Tx prefix hash: 1a861d7a58f5a74388ea6bb98f10b8a318815fee47d7875c65122d4dd0bab78d
Tx public key: d461621bae54e5859d21c93e73d127caf63ba4f1dc32a9efa2d7700cd542f8c7
Timestamp: 1737993816 Timestamp [UCT]: 2025-01-27 16:03:36 Age [y:d:h:m:s]: 00:141:02:19:49
Block: 1206334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100780 RingCT/type: yes/0
Extra: 01d461621bae54e5859d21c93e73d127caf63ba4f1dc32a9efa2d7700cd542f8c70211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c556f5f3c66855efc8d5ad3b9740129a3580ab16c72f3486018a4ee4646569fb 0.600000000000 1693037 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": 1206344, "vin": [ { "gen": { "height": 1206334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c556f5f3c66855efc8d5ad3b9740129a3580ab16c72f3486018a4ee4646569fb" } } ], "extra": [ 1, 212, 97, 98, 27, 174, 84, 229, 133, 157, 33, 201, 62, 115, 209, 39, 202, 246, 59, 164, 241, 220, 50, 169, 239, 162, 215, 112, 12, 213, 66, 248, 199, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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