Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 005ab6b580a3267198c02e37b13e56eecc6525da8ec0911ee2445d0c5f644a59

Tx prefix hash: ce7afa8161409665d3b233317f66c46f74071e3084e70db3aef6edeb78a028b2
Tx public key: fd115f4a1f4390a6444544986539e50ca7985a61e5157f41ec9d3e2bf854b021
Timestamp: 1695488048 Timestamp [UCT]: 2023-09-23 16:54:08 Age [y:d:h:m:s]: 01:258:02:24:53
Block: 854537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445578 RingCT/type: yes/0
Extra: 01fd115f4a1f4390a6444544986539e50ca7985a61e5157f41ec9d3e2bf854b021021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.904824255000 dcy

stealth address amount amount idx
00: 362faa26bdc70a9b673b77e5eeb9f5d7b520563d080acdaf38911b0ed8044531 0.904824255000 1308517 of 0

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": 854547, "vin": [ { "gen": { "height": 854537 } } ], "vout": [ { "amount": 904824255, "target": { "key": "362faa26bdc70a9b673b77e5eeb9f5d7b520563d080acdaf38911b0ed8044531" } } ], "extra": [ 1, 253, 17, 95, 74, 31, 67, 144, 166, 68, 69, 68, 152, 101, 57, 229, 12, 167, 152, 90, 97, 229, 21, 127, 65, 236, 157, 62, 43, 248, 84, 176, 33, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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