Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20b8c6d106858c5cdfcb78b036642b6410ab03f21f62efcc81860a18dd3ca2e5

Tx prefix hash: e232dc54dea06df2fe6c1a145c1549a6864c0adc66bd616fda989913f1db6887
Tx public key: 60d302eb7b39b40c0a72b12166122990d23cec924e6b7b9b42810cf19e336a86
Timestamp: 1730645259 Timestamp [UCT]: 2024-11-03 14:47:39 Age [y:d:h:m:s]: 01:006:19:47:58
Block: 1145731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263290 RingCT/type: yes/0
Extra: 0160d302eb7b39b40c0a72b12166122990d23cec924e6b7b9b42810cf19e336a860211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aec9905652f946a37de0faae7476d2574aee0fe409421c3e2e60cc759b84f51d 0.600000000000 1630224 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": 1145741, "vin": [ { "gen": { "height": 1145731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aec9905652f946a37de0faae7476d2574aee0fe409421c3e2e60cc759b84f51d" } } ], "extra": [ 1, 96, 211, 2, 235, 123, 57, 180, 12, 10, 114, 177, 33, 102, 18, 41, 144, 210, 60, 236, 146, 78, 107, 123, 155, 66, 129, 12, 241, 158, 51, 106, 134, 2, 17, 0, 0, 0, 6, 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