Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 530746863ae7fbb349b468ce3292e0a8c725df75766da7d89432c8bb7f066daf

Tx prefix hash: 3dabcb28560917f6f06e0fb9cc63bd75738493aa2bc9e1ed3a3083caddac128e
Tx public key: 263415801dd885f0357704f415db77935ee6f412aa08af1c08d5dc1ea6e1fd92
Timestamp: 1710392536 Timestamp [UCT]: 2024-03-14 05:02:16 Age [y:d:h:m:s]: 01:244:08:41:01
Block: 977923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433340 RingCT/type: yes/0
Extra: 01263415801dd885f0357704f415db77935ee6f412aa08af1c08d5dc1ea6e1fd9202110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 443d7d1b0e553bbf9fd8d877a22202e469b4fbdd84097181ec1ca183106f0ddc 0.600000000000 1437932 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": 977933, "vin": [ { "gen": { "height": 977923 } } ], "vout": [ { "amount": 600000000, "target": { "key": "443d7d1b0e553bbf9fd8d877a22202e469b4fbdd84097181ec1ca183106f0ddc" } } ], "extra": [ 1, 38, 52, 21, 128, 29, 216, 133, 240, 53, 119, 4, 244, 21, 219, 119, 147, 94, 230, 244, 18, 170, 8, 175, 28, 8, 213, 220, 30, 166, 225, 253, 146, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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