Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 453b071b0dda3a8c7c7d8d442600f1614ec5fcf789a3a9049a9a1d99e5c6f433

Tx prefix hash: aa23109247e013c30dfb04a2edaf47a6475d94ddc1332ad4cbc8b79777ff07e3
Tx public key: 2e5f1a655b10c1d8d8311bd44c7321d4b99d6c71c1bff6f8c3e4db1c8d8e25f2
Timestamp: 1719648626 Timestamp [UCT]: 2024-06-29 08:10:26 Age [y:d:h:m:s]: 00:357:10:34:02
Block: 1054639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255295 RingCT/type: yes/0
Extra: 012e5f1a655b10c1d8d8311bd44c7321d4b99d6c71c1bff6f8c3e4db1c8d8e25f202110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e85fc099230f7b914751a05ee8b705fe9989d9c2863943fc776faba689c35c5 0.600000000000 1525006 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": 1054649, "vin": [ { "gen": { "height": 1054639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e85fc099230f7b914751a05ee8b705fe9989d9c2863943fc776faba689c35c5" } } ], "extra": [ 1, 46, 95, 26, 101, 91, 16, 193, 216, 216, 49, 27, 212, 76, 115, 33, 212, 185, 157, 108, 113, 193, 191, 246, 248, 195, 228, 219, 28, 141, 142, 37, 242, 2, 17, 0, 0, 0, 5, 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